2020.01.19 02:05 "Re: [Tiff] Warnings while building tools", by Bob Friesenhahn
The nmake-based build is not as well maintained as it could be since none of the libtiff developers use it. The features provided by Visual Studio depend on version, so some manual tailoring is likely required.
Since it's not actively tested and isn't on a par with the CMake build, is it time to consider dropping it?
The CMake build should take care of these portability details just like the Autotools build does, and it's actively tested on Windows.
We should not get rid of it because the CMake build is a "self serving" build which makes the assumption that the user is using the build product as is. The Makefiles produced by CMake can not be independently used, and they even need CMake available to work.
The nmake makefiles serve as a useful example.
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt