2020.01.22 14:41 "Re: [Tiff] Warnings while building tools", by Bob Friesenhahn
On Tue, 21 Jan 2020, Edward Lam wrote:
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.
I plan to test the nmake-based build and add the few missing lines of code necessary for it to work properly again under ideal circumstances. It seems very straightforward. It is good to know that VS2019 supports strtoll and strtoull so preprocessor logic can be added to make things work automatically.
There is no guarantee of anything related to libtiff and the nmake-based build is the least supported of the three existing build infrastructures and it is not continually validated. The nmake-based build is relatively trivial and not difficult to keep working. The main problem is that this has not been recently done.
Libtiff is built as part of GraphicsMagick's Visual Studio build. Parts of the nmake-based build (particularly template header files) were used as the basis for this build. The headers output by cmake are definitely not as useful for this purpose. It is likely that other projects which don't treat libtiff as an externally-build library benefit from this useful starting point.
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt