3 ms·
The only thing I don’t like about make, is it feels like having a configure and make file sets the expectation that: ./configure make all Will actually have
by bee_rider 4y ago
The only thing I don’t like about make, is it feels like having a configure and make file sets the expectation that:
./configure
make all
Will actually have a good chance of working, which is not something my makefiles can live up to!
- thomastjeffery 4y agoI can't tell if you meant to imply this, but that is the very benefit Nix provides: a guaranteed stable and sterile environment where ./configure, make all, and make install can be run. No more chances.
- hawski 4y agoIf you have a configure step it can fail by default if there is anything to specify explicitly. But otherwise it is nice to have some defaults. In my opinion a configure script shouldn't do much in terms of detection. It should not silently enable/disable features based only on libraries being present/missing. By default it should try to use lib a and b, if the user wants they could explicitly opt-in to use lib c without lib b, otherwise let it fail. That said it all makes it easier to just use config for make that can be edited. For example config.mk included by Makefile. I learned this trick from Suckless.