2020.01.22 03:07 "Re: [Tiff] Warnings while building tools", by Edward Lam
IMHO, cmake provides extra features with the trade off of added complexity. Out of the myriad of third party libraries that we use, it's the nmake ones that provide the least pain for me whenever I upgrade to a new Visual Studio version. nmake at least still works when I upgrade to the latest Visual Studio and doesn't require that I also upgrade cmake in order to use it.
Given the way the world is though, I concede it's probably better in the long run to switch to cmake for:
- better maintainability
- consistent cross-platform build system
- ability to take advantage of parallel builds
But I think we should do so with full knowledge that things will get better but also more complex than before for Windows users.
On 1/21/2020 3:03 PM, Roger Leigh wrote:
As an example relevant to this discussion, VS2019 supports strtoll and strtoull, so if you configure with this version of MSVC, you should get the native CRT functions used automatically, not the compatibility reimplementations.
To be honest, this is a bad example. The compatibility layer should just automatically choose to do the right thing using predefined and well-known macro definitions. This is the part where I want this stuff built into the code itself and not in the build system.
My 2 cents as a bystander. :)