That time of the year when I feel the urge to write my own build/integration system again.
[#]Bazel is a pain to extend and has many idiosyncracies. Also code base is way too complex and hard to penetreate. It feels generally stuck in a local maximum.
[#]Buildstream is pretty cool and extensible but variation support is not very elegant. It also still needs an inner build system. Also yaml 😒
[#]Pants seemed to be a step in the right direction. Amazingly simple extensibility. But still felt like the the build variation capabilites were not that strong. Also no support for C++.
I like starlark itself.
Does anybody know of any build system "framework" which I can just plug an play on a build tree so that I don't have to write the ugly parts of dealing with the compiler and focus on building the nice constructs for describing that build tree?
=> More informations about this toot | More toots from matzipan@hachyderm.io
@matzipan depends on circumstances mostly. Build systems like these are overkill for personal projects.
If your repo has only one language, then one could just use the language native tools (pip, esbuild, etc.).
Sure, you won’t get nice features like incremental builds and parallel execution, but at least you won’t feel like you are taming a dragon like you would while trying to get Bazel to work.
=> More informations about this toot | More toots from bennine@mastodon.world
@bennine I'm talking about #c++ build systems
=> More informations about this toot | More toots from matzipan@hachyderm.io This content has been proxied by September (ba2dc).Proxy Information
text/gemini