Am Fri, 30 May 2025 12:13:44 +0200 schrieb Branko Čibej <br...@apache.org>:
> In light of which you'll be happy to know that Subversion's autotools > build isn't going anywhere and will remain the preferred build system > for Unix-like platforms. > Microsoft's tooling. CMake is basically a buffer for that, Thanks for the info. Incidentally, that 's also the situation with a project I manage, mpg123, where CMake entered the picture as a contribution, an additional 'port' like other specific Makefiles before mpg123 itself switched to autotools around 2006 or so. This 'port' replaced the manually-curated MSVC project files that existed before and while I occasionally have to fix up the CMake build and ensure that it at least is not totally broken, it is not the main build system with all options that autotools build has — and the MSVC build isn't even complete in that it only supports building libraries, not the end-user programs. Though, certain packaging systems (esp. those targetting Windows) like to use the cmake variant and are able to get libmpg123 integrated as a dependency in their package sets via that route. This does mean that I do get bug reports about both build systems and there is additional work, but with CMake I am at least able to somewhat help MSVC folks without having to touch that application myself. It is annoying having to solve problems like building preprocessed assembly twice, for two build systems, hence most projects eventually end up deprecating the older one. I'm just too stubborn for that. Already autoconf seemed like a big complication to me back then … and it is. Let's not pretend that any build system doesn't suck;-) Alrighty then, Thomas -- Dr. Thomas Orgis HPC @ Universität Hamburg
