3 ms·
I liked Make due to my perceived simplicity of it. Thanks to this article, I think I'll just use Rake next time.
by schnable 7y ago
I liked Make due to my perceived simplicity of it. Thanks to this article, I think I'll just use Rake next time.
- pferde 7y agoI like make because it can be as simple as you want it, yet powerful if you need it to be.
- megous 7y agoFor real simplicity I like ninjabuild. I use it in cases where Makefiles would be a real mess to maintain and in general where I want to paralelize a set of file transforming jobs and have a nice progress indicator and ability to cancel and continue. I just have a nice PHP generator class for ninja files and I build ninja files programatically in a real programming language based on whatever I like. With this approach it's possible to fully parallelize builds accross however many different toolchains and SDKs with relative ease and without need to deal with quirks, or limitations of languages of various build systems or build tools that try to be semi-universal (like GNU make) but are not, or have a lot of non-obvious magic integrated. And I also live how ninja tracks changes in its own build rules and automatically rebuilds targets that would be affected, which is what I always disliked about makefiles. If you change makefile rule you basically have to do `make clean ; make`.
- sounds 7y agoI'll second you on ninjabuild. I just wish https://github.com/ninja-build/ninja/pull/1578 https://github.com/ninja-build/ninja/pull/1578 would get merged, so I can compose ninjabuild repos seamlessly.