I stopped feeling bad about #autotools files (configure.ac Makefile.am m4/*) when I realized how much noise a new maven package throws on your disk.
The main difference is: for #maven / #npm / #cargo / #gradle / #bazel / ... these are autogenerated.

That’s why I started #conf: https://hg.sr.ht/~arnebab/conf — auto-generation for autotools projects with `conf new --lang <language>`.

It needs more templates … contributions welcome!
(just send me a patch or a link to pull from)
#gnu #make #freesoftware

Running bazel build on macOS in zellji/screen, then in a normal shell, invalidate the other terminal's cache. Running bazel under nix develop in both terminals preserves the cache because the $PATH is the same. #bazel #nix

Hermetic run scripts built with bazel are addictive to configure. Iterate until every input file and environment variable is explicitly defined. I did this for aws cli wrappers for a bucnh of AWS accounts. #bazel

@GeePawHill I know you’re not actually looking for a sensible answer, but #bazel extensions are written in a subset of python called “starlark” and they’re mostly Open Source and kept on GitHub.

Want to know how this rule works? The IDE integrations allow you to click through build files just as easily as through source code. Minimal magic….

Just posted about how #bazel’s history pokes into its current UX: https://blog.rocketpoweredjetpants.com/2023/05/your-roots-are-showing/

The `distro(less) images` concept is a way of restricting what's in your runtime container to precisely what's necessary for your app, which is a best practice employed by Google ☝️
A great article that shows how you can achieve this on your own with the help of the #Bazel tool↙️
https://www.infoq.com/news/2023/06/bazel-rules-oci-distroless-image/?utm_campaign=infoq_content&utm_source=twitter&utm_medium=feed&utm_term=Devops

Set up a project with #Bazel for building #Android #apps📱 By @Neurenor

https://www.droidcon.com/2023/04/19/bazel-the-revolutionary-build-system-for-android-app-development/

When I introduce #bazel to people, I end up discussing the history of where it came from, and how it’s roots show up almost everywhere. Wondering if I should write a blog post or create a video going through some of this.

Pros: it’s interesting, and it helps explain some weirdness in the tool
Cons: I wonder how happy Google would be to have this out there.

Should I do it?

I started writing a toot-storm, but I realized a blog post was a better medium for it. Enjoy:

https://www.buildbuddy.io/blog/multiple-xcode-configurations-with-rules_xcodeproj-1-3

#rules_xcodeproj #Bazel #Xcode

Me: Hey #Bazel, what depends on "golang.org/x/net" in my repo?

Mr.Bazel:

---

I will use this image in a future slide. And it's only 1/8 of the actual SVG file 😤

I’m compiling `protoc` from source. Now I know I’m using #bazel 😁

I’m so excited to announce we’ve released version 1.0 of #rules_xcodeproj!

For a release this important, I’ve written a blog post. Please enjoy 😊.

https://www.buildbuddy.io/blog/introducing-rules_xcodeproj-1-0

#Bazel #Xcode

@frozencanuck a new resolver for #bazel rules_jvm_external. Under the covers it does dependency resolution using the resolvers from gradle or maven, but then we hand back to a custom utility to allow us to download everything in parallel. https://github.com/bazelbuild/rules_jvm_external/pull/807

Hands up who knew that the #maven coordinates for an artifact don't actually declare where the artifact is?

I knew that the pom.xml contained a bunch of information about dependencies, but it can also contain things like the default packaging to use, or handle relocations.

This makes my simple downloader to maven coordinates to use in #bazel projects a lot harder to write. *sigh*

@kytta Save your sanity with #Bazel

First time trying out #bazel bzlmod and I just hit with a module not found? I guess i'll check back in 6 months

I happy to announce that I’ve just released version 0.12 of #rules_xcodeproj!

Like the release before it, I didn’t plan to have another release before the 1.0 release candidates, but since a fair amount of improvements and bug fixes made it in, I felt it wasn’t worth waiting to get these changes out.

Please read the release notes (https://github.com/buildbuddy-io/rules_xcodeproj/releases/tag/0.12.0) for a detailed account of what is included in this release.

#Bazel #Xcode

For this reason, companies such as Tesla https://www.youtube.com/watch?v=ol5hwjr48Q4 has been looking into cloud solution: by leveraging the shared power compute in the data center, you can improve the developer experience for critical workload like such.

At the key of all these is #Bazel and the ability to granularly split up your build into thousands of small actions that can be parallel executed on top of a build farm, shared between hundred of users.

Google casually mentioned that they use a custom hash algorithm for their internal build tool #bazel is mind-blowing.

https://github.com/bazelbuild/remote-apis/pull/235#issuecomment-1360889983

I barely know what AVX2 is. Git is still having a really hard time getting off SHA1 into SHA256. And these guys said "oh we have been passed all that since 2018"... 🤣

Before taking some time off for the holidays, I thought it would be nice to have another release of #rules_xcodeproj: https://github.com/buildbuddy-io/rules_xcodeproj/releases/tag/0.11.0.

I hadn’t planned on having another release before the 1.0 release candidates, but we made a couple of nice fixes and performance improvements, so it seemed like a good idea. I’m not going to go into detail on the changes, the release notes do a good job of that for this release.

Hopefully the next release is 1.0-rc1 😊.

#Bazel #Xcode