Configure script purpose

[Adriankhl]

Originally Posted by Flambard

This is a bit disingenuous, it appears you know precisely, what "configure" is, you just don't like it.

The actual script is NOT 7000+ lines long, it's more like 600. https://github.com/angband/angband/b...r/configure.ac

The generated script works on everything that has a shell (not even bash, just any shell), thus it's completely dependency-free, which is the purpose.

Yes, autoconf syntax is a bit terse, but is CMakeLists.txt really better? And yeah, autoconf has some problems, but so does CMake.

Just my 2 cents, before jumping into next build system, maybe we should examine if that's even necessary?

Depends on how much do you love Windows, cmake integrates much better with different compilation settings on Windows. For example, how can autotools manage clang-cl + vcpkg + windows SDK?

[fph]

Originally Posted by Adriankhl

Depends on how much do you love Windows

If you put it this way, I'm not sure it's an argument in your favor.

[Adriankhl]

Originally Posted by fph

If you put it this way, I'm not sure it's an argument in your favor.

Well, like it or not, the dominance of Windows desktop is not going away. I used to hate Windows. However, I am starting to realize the importance of big companies behind open source software, and Microsoft is getting better these days. If we cannot ignore the presence of Windows, and there are existing open source, cross-platform solutions, why not love Windows (and ourselves ) more to make use of those tools.