3 ms·
Also I should mention one big difference between Bazel/Blaze and GN (and Gyp) is that the latter doesn't do the actual build, it generates a build that Ninja ex
by cmrdporcupine 5y ago
Also I should mention one big difference between Bazel/Blaze and GN (and Gyp) is that the latter doesn't do the actual build, it generates a build that Ninja executes, instead.
Blaze owns the whole thing, executes the toolchain, etc.
Blaze is also very much built for the monorepo model we had in Google3. Not that it won't work in other scenarios, but that's where it came from: one repo and when it comes to third party dependencies, one version, etc. And cross-compiling on it felt awkward. GN/Ninja support for multiple toolchains and cross-compiling felt more thought-through, by necessity.
- p_l 5y agoIt seems that with current level of Bazel toolchain support it becomes much easier to crosscompile. Well, something I'll test hopefully somewhat soon, as I want to test bazel explicitly in very crosscompiling environment...
- cmrdporcupine 5y agoIt is done by some teams at Google, so definitely possible to do it decently enough to ship something.
- p_l 5y agoMy goal is to build bazel support for Ada, including building of crosscompilation toolchains and platform runtimes. Will see how it will work out :)
- lima 5y ago> GN/Ninja support for multiple toolchains and cross-compiling felt more thought-through, by necessity. I'd argue this is still the case right now, but toolchain support in Bazel is maturing quickly.