71–80 of 180 posts
I've looked at Bazel some time ago but it was lacking full Swift support. There's some mentions to Swift scattered across the docs but some of them lead to 404 pages[1]. Has anyone gotten a Swift + Objective-C project running on Bazel or should I stay with Facebook's Buck? [1]: https://github.com/bazelbuild/rules_apple/blob/master/doc/ru... Edit: Found the correct links for the Swift/Apple support docs. https://githu…
The only contact I’ve had with bazel is via Tensorflow (more specifically tf lite). Last I tried it was not possible to set up bazel to output a static library. Has this changed?
--dynamic_mode=offEarlier quoted context omitted.
I did a quick skim and it doesn't seem to sandbox the build steps like Bazel? Maybe I missed something.
It doesn't do Bazel's style sandboxing where your entire compiler toolchain is part of your build system. It does what we call high-fidelity builds : it tracks changes not only to inputs but also to compile options, compiler itself (checksum), environment, etc., and if any of these auxiliary dependencies change, it triggers a rebuild. There are advantages and disadvantages to both approaches with build2's being light…
Woo hoo! I got to spend a few days with the Bazel team in the NYC office a few weeks ago and they were really excited about this announcement coming out soon. Congrats! One of my favorite uses of Bazel is in CI/CD. I built a demo which builds the applications, creates Docker images, and then applies a K8s manifest to a cluster. It's OSS now under the GCP handle: https://github.com/GoogleCloudPlatform/gke-bazel-demo H…
Earlier quoted context omitted.
If only Android team cared to use it instead of Gradle. Android is probably the only platform where almost at every conference there is a regular talk on how to improve build times. Not even C++ conferences talk so much about build times.
I find gradle is something like doing thing diligently what should not be done in first place. It seems clear though Oracle/OpenJDK have no interest in putting some fucking options in `javac` itself to compile project/module or even package. Users must wade through maven/gradle crap every time even to compile pure Java projects.
I used to compile Java projects since 1996 until 2004 pretty alright.
And Maven runs circles around Gradle's performance, without requiring a background daemon sucking up at least 2GB, minimum.
Gradle is the only reason Groovy is still somehow relevant and it has to thank Google's Android team for it.
As for the Oracle/OpenJDK remark, it is an open source project, under the GPL with Classpath exception license, it is up to the ones that keep saying that Oracle doesn't do a good job to contribute.
Bazel may be 1.0 and the internal abstractions of dag solving etc are rock solid from years of use inside Google, but the ecosystem around Bazel is quite bad at the moment. They've been breaking backwards compatibility constantly, so rules authors have struggled to keep up (hopefully done now that it's 1.0). The reason the ecosystem maturity is so important for bazel is because its design encourages complete reimplem…
So in order to benefit from the two, it would likely require GCB to work with Bazel natively and also to have some powerful state abstractions in order to optimize builds in a distributed fashion.
Earlier quoted context omitted.
It doesn't do Bazel's style sandboxing where your entire compiler toolchain is part of your build system. It does what we call high-fidelity builds : it tracks changes not only to inputs but also to compile options, compiler itself (checksum), environment, etc., and if any of these auxiliary dependencies change, it triggers a rebuild. There are advantages and disadvantages to both approaches with build2's being light…
I don't see how build2 can be in the same spirit as Bazel when it misses the main advantage of Bazel
Bazel may be 1.0 and the internal abstractions of dag solving etc are rock solid from years of use inside Google, but the ecosystem around Bazel is quite bad at the moment. They've been breaking backwards compatibility constantly, so rules authors have struggled to keep up (hopefully done now that it's 1.0). The reason the ecosystem maturity is so important for bazel is because its design encourages complete reimplem…
I've noticed this as well. I'd love to use Bazel for our Python 3 project, but as far as I can tell, the advertised Python 3 support doesn't actually work. There are several issues filed for this, but apparently no progress since 2018. Some people reported workarounds, but none that I could reproduce.
I believe the core is solid, but language support feels alpha at best.