- 2020.01.18 16:03 "Re: [Tiff] Warnings while building tools", by Greg Troxel
-
2020.01.18 21:32 "Re: [Tiff] Warnings while building tools", by Bob Friesenhahn
-
2020.01.18 22:29 "Re: [Tiff] Warnings while building tools", by Roger Leigh
-
2020.01.19 02:05 "Re: [Tiff] Warnings while building tools", by Bob Friesenhahn
-
2020.01.19 11:51 "Re: [Tiff] Warnings while building tools", by Even Rouault
-
2020.01.19 15:13 "Re: [Tiff] Warnings while building tools", by Greg Troxel
-
2020.01.19 15:54 "Re: [Tiff] Warnings while building tools", by ZdPo Ster
-
2020.01.19 16:53 "Re: [Tiff] Warnings while building tools", by Roger Leigh
- 2020.01.19 19:41 "Re: [Tiff] Warnings while building tools", by Bob Friesenhahn
-
2020.01.19 16:53 "Re: [Tiff] Warnings while building tools", by Roger Leigh
-
2020.01.19 15:54 "Re: [Tiff] Warnings while building tools", by ZdPo Ster
-
2020.01.19 15:13 "Re: [Tiff] Warnings while building tools", by Greg Troxel
-
2020.01.19 11:51 "Re: [Tiff] Warnings while building tools", by Even Rouault
-
2020.01.25 16:22 "Re: [Tiff] Warnings while building tools", by Bob Friesenhahn
-
2020.01.25 20:24 "Re: [Tiff] Warnings while building tools", by Bob Friesenhahn
-
2020.01.26 16:37 "Re: [Tiff] Warnings while building tools", by Jeff McKenna
- 2020.01.26 16:39 "Re: [Tiff] Warnings while building tools", by Jeff McKenna
- 2020.01.26 17:34 "Re: [Tiff] Warnings while building tools", by Miguel Medalha
-
2020.01.26 16:37 "Re: [Tiff] Warnings while building tools", by Jeff McKenna
-
2020.01.25 20:24 "Re: [Tiff] Warnings while building tools", by Bob Friesenhahn
-
2020.01.19 02:05 "Re: [Tiff] Warnings while building tools", by Bob Friesenhahn
- 2020.01.22 12:25 "Re: [Tiff] Warnings while building tools", by Miguel Medalha
- 2020.01.29 14:14 "Re: [Tiff] Warnings while building tools", by Bob Friesenhahn
-
2020.01.18 22:29 "Re: [Tiff] Warnings while building tools", by Roger Leigh
- 2020.01.19 17:32 "Re: [Tiff] Warnings while building tools", by Miguel Medalha
2020.01.29 14:31 "Re: [Tiff] Warnings while building tools", by Jeff McKenna
Works well with MSVC 2017
Thank you Bob
-jeff
On 2020-01-29 10:14 a.m., Bob Friesenhahn wrote:
I have now pushed what should hopefully be the last simplification to
> the nmake build. This is the description that I entered for the two
relevant commits:
"Make sure that tif_config.h is produced prior to entering the port directory and add an include path so that the port files can include
> tif_config.h. Do not actually include tif_config.h at this time since > CMake and Autotools builds are not prepared for that. This issue could
be handled by updating the CMake and Autotools builds or by adding a define which directs libport.h to include tif_config.h."
> "Simplify nmake configuration for building port directory. Now there is
only one boolean setting to enable building strtoll() and strtoull()
> port functions. The boolean setting enables the necessary port files to
be built, but the remainder of the logic is via pre-processor code in the common tif_config.h, which was prepared before entering the port directory to do a build."
Now there is only one boolean setting in nmake.opt, which is default enabled:
# Indicate if the compiler provides strtoll/strtoull (default 1) # Users of MSVC++ 14.0 ("Visual Studio 2015") and later should set this to 1
HAVE_STRTOLL = 1
> I have tested this with Visual Studio 2008 and 2019. Independent