Le 15/12/2021 à 20:30, Nalini Vishnoi a écrit :
Thank you so much, Even!! 😊
Got it, somehow I wasn’t able to see that comment before – thanks for
sharing the direct link (‘c’ flag in TIFFOpen() is really interesting).
One last question (hopefully):
I built the library on Linux using configure and
-disable-strip-chopping option but somehow I am still able to see the
strip chopping enabled by default. Am I missing something here?
The option works fine for me. But make sure you put a double dash before
disable-strip-chopping
Many thanks,
Nalini
*From:* Even Rouault <[email protected]>
*Sent:* Thursday, December 9, 2021 6:10 AM
*To:* Nalini Vishnoi <[email protected]>; [email protected];
[email protected]; Bob Friesenhahn <[email protected]>
*Subject:* Re: [Tiff] Windows - difference in behavior when large
RowsPerStrip is specified while writing Uncompressed vs LZW compressed
TIFF file
1. With the “long” fix, I can now read back the LZW compressed
file successfully on Windows so indeed the root cause was
“long” datatype used in tif_lzw.c which worked on Linux (64
bit) but failed on Windows (32 bit) as Paavo had suspected.
Cool. I just merged the merge request into master
Not sure which response you referred to when you said “See my
previous response”? Do you mean explanation here:
https://www.asmail.be/msg0054930920.html?
<https://www.asmail.be/msg0054930920.html?>?
No, a message posted just a few hours before:
https://www.asmail.be/msg0055227723.html
<https://www.asmail.be/msg0055227723.html>
--
http://www.spatialys.com <http://www.spatialys.com>
My software is free, but my time generally not.
--
http://www.spatialys.com
My software is free, but my time generally not.
_______________________________________________
Tiff mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/tiff
