2012.04.17 17:25 "Re: [Tiff] LZW Support configuration issue", by Christopher Cameron
Bob, you were right that I was using "a mix" of libtiff. I was deploying my .so's to the incorrect location on the target's filesystem, which resulted in both versions (one with LZW, one without) being available. It looks like the one without LZW support was being used at runtime. I am now deploying to the correct location and LZW support works fine.
Thanks a lot,
Software Developer - Multimedia/Camera
On 12-04-09 9:07 AM, "Christopher Cameron" <firstname.lastname@example.org> wrote:
I am just using libtiff 4.0.0; I don't have any other version to work with. I am building it as part of another product's "make install" procedure which makes use of the libtiff configuration. I am able to use libtiff in my applications without a problem for decoding and encoding. But I cannot seem to get LZW support to work, even when tiff_config.h says that it is configured with "#define LZW_SUPPORT 1".
On 12-04-05 4:27 PM, "Bob Friesenhahn" <email@example.com> wrote:
I am currently re-configuring libtiff 4.0.0 to support LZW.
As far as I understand, all I had to do was re-run configure without the "--disable-lzw" option, rebuild, and then rebuild my code which makes use of libtiff. All seems well in the code - LZW_SUPPORT is defined, and the code in tif_lzw.c is not inactive anymore (in the editor, I mean).
LZW is indeed supported by default for many years now.
But when I run my code, I get the following error:
\X$x5 compression support is not configured
Quite strange how what probably should read "LZW" reads "\X$x5" and in fact this has also been "\X x5" and various other unsavory looking characters (hah).
Probably you are still using some archaic libtiff rather than the one you just built, or a mix of both. Did you remember to do 'make install' to put the build product where your own software can find it?