3 ms·
>Long build times This is one of the major ones for me. It's a multiplier for everything else. local builds, CI builds, feedback cycles. If you get your build
by carlmr 3y ago
>Long build times
This is one of the major ones for me. It's a multiplier for everything else. local builds, CI builds, feedback cycles. If you get your build times down, everything else gets faster.
Migrating to Bazel was a godsend, while Bazel isn't perfect, it's one of the best build systems for large C++ (or mixed) code bases I've seen. buck2 looks promising, too, in this regard.
- kridsdale1 3y agoHaving used both I vote for Buck2 being a bit better in dev experience for performance, resource usage, and sensible config language.
- carlmr 3y agoI'm intrigued by Buck2, do you have good resources on learning it? Last time I checked it was still a bit early and I had issues finding out how to migrate our Bazel build to Buck 2. The single phase build is amazing as a concept.
- kridsdale1 3y agoIt was an internal (not yet open source) tool when I used it, so the docs and people behind it were much more available to me than it would be now as a public project.
- carlmr 3y agoAh, gotcha. I tried installing it and the first thing it gave me was an error message. I googled it, couldn't find the answer. Got an answer now, it worked for a small toy example at least. But I haven't gotten around to try it out further. I feel like the dev experience - without internal help for initial setup - isn't quite there yet, especially regarding error messages and documentation.