AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2021.04.14 16:48 "[Tiff] 4.3.0 release ?", by Even Rouault
2021.04.14 18:15 "Re: [Tiff] 4.3.0 release ?", by Miguel Medalha
2021.04.14 18:23 "Re: [Tiff] 4.3.0 release ?", by Even Rouault
2021.04.14 18:31 "Re: [Tiff] 4.3.0 release ?", by Miguel Medalha
2021.04.14 18:51 "Re: [Tiff] 4.3.0 release ?", by Miguel Medalha
2021.04.14 19:00 "Re: [Tiff] 4.3.0 release ?", by Even Rouault
2021.04.14 19:20 "Re: [Tiff] 4.3.0 release ?", by Miguel Medalha
2021.04.14 19:23 "Re: [Tiff] 4.3.0 release ?", by Miguel Medalha
2021.04.14 19:33 "Re: [Tiff] 4.3.0 release ?", by Even Rouault
2021.04.14 19:38 "Re: [Tiff] 4.3.0 release ?", by Miguel Medalha
2021.04.14 19:46 "Re: [Tiff] 4.3.0 release ?", by Even Rouault
2021.04.14 20:05 "Re: [Tiff] 4.3.0 release ?", by Miguel Medalha
2021.04.14 20:13 "Re: [Tiff] 4.3.0 release ?", by Even Rouault
2021.04.14 20:34 "Re: [Tiff] 4.3.0 release ?", by Miguel Medalha
2021.04.14 20:47 "Re: [Tiff] 4.3.0 release ?", by Even Rouault
2021.04.14 22:12 "Re: [Tiff] 4.3.0 release ?", by Miguel Medalha
2021.04.14 22:14 "Re: [Tiff] 4.3.0 release ?", by Miguel Medalha
2021.04.14 22:23 "Re: [Tiff] 4.3.0 release ?", by Miguel Medalha
2021.04.14 22:25 "Re: [Tiff] 4.3.0 release ?", by Even Rouault
2021.04.14 22:31 "Re: [Tiff] 4.3.0 release ?", by Miguel Medalha
2021.04.14 22:40 "Re: [Tiff] 4.3.0 release ?", by Miguel Medalha
2021.04.14 20:38 "Re: [Tiff] 4.3.0 release ?", by Even Rouault
2021.04.14 20:41 "Re: [Tiff] 4.3.0 release ?", by Miguel Medalha
2021.04.14 19:25 "Re: [Tiff] 4.3.0 release ?", by Jeff McKenna
2021.04.14 20:05 "Re: [Tiff] 4.3.0 release ?", by Bob Friesenhahn

2021.04.14 20:13 "Re: [Tiff] 4.3.0 release ?", by Even Rouault

Could you check if you have several tif_config.h around (it should normally be in {build_path}/libtiff/tif_config.h, but if there are other tif_config.h accessible through inclusion that might create confusion), and what its content is.

That seemed to be the case. There was a previous version of 'tif_config.h' under 'C:\build\include', for use with other projects. This 'automatic finding' of something we didn't explicitly specify, and in fact specified otherwise on the cmake command line by "-DJPEG12_LIBRARY:FILEPATH=C:\build\lib\jpeg-static-12bit.lib -DJPEG12_INCLUDE_DIR:PATH=C:\build\include\jpeg12", makes the whole thing harder to manage...

Is that line in ' tif_jpeg_12.c ' really necessary? The header and library for 12-bit jpeg are correctly found by specifying their locations on the cmake command line.

yes, it is. Otherwise you're likely going to use symbols of the 8-bit libjpeg. It might build fine, but at runtime, you won't be able to read 12-bit jpeg compressed files.

http://www.spatialys.com
My software is free, but my time generally not.