3 ms·
My memory of GNU autotools and friends, from when I shipped one release of a project with it: * the size of my project doubled * naturally, autotools would ch
by souprock 6y ago
My memory of GNU autotools and friends, from when I shipped one release of a project with it:
* the size of my project doubled
* naturally, autotools would check for FORTRAN despite my project being in C
* if users built the software as root, it would trash critical system files
* instead of installing ELF library files in /lib, it installed non-functional shell scripts in /usr/lib
* cross compiling broke
The solution was plain old make. You can do a lot with make. It performs really well. I even did a "make install" that would depend on the final locations for everything. It was all configurable. It worked great.
- nrclark 6y agoI've used autotools on a ton of my projects, and I like it a lot. I can't speak to any of the problems you had. The one thing I'll say about Autotools is that the learning curve is pretty steep, and it took a fair amount of experimentation to get it right on my first Autoolized project. Maybe you never made it all the way over the hump?