4 ms·
Yeah terrible idea. Either you should commit the output of autoconf (and enforce keeping it up to date via CI), or much much better - stop using autoconf! It be
by IshKebab 3y ago
Yeah terrible idea. Either you should commit the output of autoconf (and enforce keeping it up to date via CI), or much much better - stop using autoconf! It belongs in the 90s!
- knorker 3y agoIt's another case of that "yes, it sucks. But the alternatives just plain don't work, or work in WAY fewer circumstances". If I have a strange architecture or install, autoconf is often the only one that works.
- IshKebab 3y agoWhat strange architecture are you talking about? I don't think the cost of supporting dead architectures is worth it. CMake is a clear better choice (it also sucks but it sucks waaaay less).
- knorker 3y agoI didn't want to start shitting on alternatives, but cmake is in my experience clearly the worst of all options. It seems that more often than not, cmake setups work on the developer's own machine and nothing else. And the choice of undocumented "-DSOMETHING" is about as user hostile as it gets.