3 ms·
Well if can't be made to work on Windows then it's not a worthwhile replacement for autoconf because autoconf does every job on all environments except Windows
by aurora72 11y ago
Well if can't be made to work on Windows then it's not a worthwhile replacement for autoconf because autoconf does every job on all environments except Windows already, why need a replacement?
To do the job on Windows, I use CMake and CMake is my autoconf replacement on Windows. Actually, if I was willing to spend some time to configure MinGW & MSYS to make autoconf work on Windows, I wouldn't need to use the CMake either .)
- 2bluesc 11y ago> To do the job on Windows, I use CMake and CMake is my autoconf replacement on Windows. Actually, if I was willing to spend some time to configure MinGW & MSYS to make autoconf work on Windows, I wouldn't need to use the CMake either .) Why not just use cmake and be done? Less dependencies? Every time I use cmake I wonder how I ever managed to use autotools or (even straight Makefiles). Especially when things like 'ctest' just work and are waiting for me to write unit-tests to utilize them.