|
Yes if you are targetting a specific set of architectures and compilers would not argue it is more efficient to use simpler build methods.
But if you want to write something with library quality usefulness then being independent of these things is important. Different configurations should require different builds if being totally generic.
You are likely locked into the Microsoft ecosystem. But at this day and age that is rather niche. Professional programmers can go cross architecture and cross platform and cross compiler quite readily.
Getting off topic though, for this project which is very Windows specific, of course CMake is overkill. But there are still several of C compilers on Windows, MSVC isn't the only possibility.
The main point is these batch file type issues are completely solved by modern build tools. Whereas making a project that can be shared and built without any issues isn't so easy with custom build processes.
|