Basically the most important thing I want out of a build system is "never put me in a situation where the method for invoking you is so convoluted I need a second build system ("script") just to execute you"
Conversation
Notices
-
Embed this notice
mcc (mcc@mastodon.social)'s status on Wednesday, 06-Mar-2024 13:12:54 JST mcc -
Embed this notice
Noel Berry (noelfb@mastodon.social)'s status on Wednesday, 06-Mar-2024 13:12:51 JST Noel Berry @mcc getting very close to completing the full circle where we need build scripts to generate cmake files which generate build scripts which compile your program.
-
Embed this notice
Noel Berry (noelfb@mastodon.social)'s status on Wednesday, 06-Mar-2024 13:12:51 JST Noel Berry @mcc stack overflow post: Yeah, this is why I recommend CMakeMake, you shouldn't ever really need to touch CMake files yourself.
Kit Rhett Aultman repeated this. -
Embed this notice
Farbs (farbs@mastodon.social)'s status on Wednesday, 06-Mar-2024 13:12:51 JST Farbs @noelfb @mcc Mentally I keep build systems in a bucket marked "Abstraction layers over trivial problems". I also keep spiders in there, to discourage me from pulling anything out.
-
Embed this notice
mcc (mcc@mastodon.social)'s status on Wednesday, 06-Mar-2024 13:12:52 JST mcc (Note: The stackoverlfow I paste there actually does have a second person giving a pure-CMake way of solving this problem. It's just… it's just that the pure CMake way is way, way worse.)
-
Embed this notice
mcc (mcc@mastodon.social)'s status on Wednesday, 06-Mar-2024 13:12:53 JST mcc I would consider "I need one build system to build, and then a second build system to copy the files the first build system needs into place and copy the files the first build system generated where they need to go afterward" to be a subset of this same problem; basically anything that results in me writing a shell script in which one step is invoking the build system means the build system has failed.
-
Embed this notice