2020.01.19 11:51 "Re: [Tiff] Warnings while building tools", by Even Rouault

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.

That's a reasonable one, isn't it? All other projects I can think of make the same assumption, and that applies to the autoconf build as well. If the user wants do embed libtiff directly in their application and bypass libtiff.so/dll or do anything custom, they're on their own.

The Makefiles produced by CMake can not be independently used, and they even need CMake available to work.

That's expected for a CMake build. CMake is pretty much mainstream to build a large number of open source projects on Windows. Not really a very exotic requirement in my opinion.

I'd be much in favor in dropping the nmake build as well. libtiff doesn't need 3 build systems IMHO.

Even

--
Spatialys - Geospatial professional services
http://www.spatialys.com