Hi Bob,
Thank you so much for your quick response!
I was able to get the shared library name changed on Linux and Mac by editing
the "configure" file (not "configure.ac") and running autoconf. I'm still not
sure if it was this file or "configure.ac" I was supposed to change. Could you
please let me know whether I was also supposed to edit "configure.ac"?
I'll also try your suggestion of running the autogen.sh script and the
-enable-maintainer mode option.
Thank you!
ellen
From: Bob Friesenhahn <bfrie...@simple.dallas.tx.us>
Sent: Wednesday, October 25, 2023 4:26 PM
To: Ellen Johnson <ell...@mathworks.com>
Cc: tiff@lists.osgeo.org
Subject: Re: [Tiff] libtiff configure questions on linking to different jpeg
shared library name?
On Wed, 25 Oct 2023, Ellen Johnson via Tiff wrote:
> Hi libtiff developers!
> We just upgraded to libtiff v4.6.0 and want to build it with our recently
> added libjpeg-turbo v3.0.0.
> Unfortunately we had to symbol version libjpeg-turbo on Linux (on
> top of its existing symbol versions) to avoid symbol collisions with
> other libjpeg versions. As part of this work, we slightly modified
> the libjpeg-turbo shared library name on Linux, Mac, and Windows -
> for example on Linux, instead of the shared library
> libjpeg.so.62.4.0, we named it libmwjpeg.so.62.4.0.
The need to do this is most unfortunate. I was wondering about this
issue.
> In our libtiff makefile, we use configure on Linux and Mac and CMake on
> Windows. I think I figured out the CMake option to link libtiff to our
> libjpeg-turbo DLL, but I'm not sure how to modify the libtiff configure
> scripts to get Linux and Mac to do the same.
> I see in the libtiff main folder there's both a configure and configure.ac
> file, and both have commands that link to libjpeg - "-ljpeg". I tried
> changing this in both files to "-lmwjpeg" instead but that didn't work. Could
> you please let me know which file or files I need to modify, and whether I
> need to manually run autoconf or similar tools after I make the change?
You can run the 'autogen.sh' script at the top of the libtiff source
tree. Even better than this, is add the --enable-maintainer-mode
option when running the configure script since then the build will
take care of itself after you edit a file.
You will need to make sure that Autotools (Autoconf, Automake, and
libtool) are installed on your system.
Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us<mailto:bfrie...@simple.dallas.tx.us>,
http://www.simplesystems.org/users/bfriesen/<http://www.simplesystems.org/users/bfriesen>
GraphicsMagick Maintainer,
http://www.GraphicsMagick.org/<http://www.GraphicsMagick.org>
Public Key,
http://www.simplesystems.org/users/bfriesen/public-key.txt<http://www.simplesystems.org/users/bfriesen/public-key.txt>
_______________________________________________
Tiff mailing list
Tiff@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/tiff
