LibTiff Mailing List
TIFF and LibTiff Mailing List Archive
October 2004
Previous Thread
Next Thread
Previous by Thread
Next by Thread
Previous by Date
Next by Date
Contact
The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems
Thread
2004.10.24 14:56 "Re: [request] add --rpath for jpeg and zlib", by Bob Friesenhahn
On Sun, 24 Oct 2004, Norihiko Murase wrote:
> [05]% ./configure \
> --prefix=/usr/local/tiff \
> --disable-old-jpeg \
> --with-zlib-include-dir=/usr/local/zlib/include \
> --with-zlib-lib-dir=/usr/local/zlib/lib \
> --with-jpeg-include-dir=/usr/local/jpeg/include \
> --with-jpeg-lib-dir=/usr/local/jpeg/lib
It was a bad idea to include support for these options (particularly
*-lib-dir) since they are difficult to implement portably or in a way
which satisifies all user expectations.
> The solution for this problem is to add the --rpath option
> when you build libtiff.so and the tools.
Using this option will not please everyone. In particular, it will
make Linux and some *BSD users/maintainers very angry.
There are two major schools of thought:
o Packages should not know where the libraries they depend on are
installed since the system can be configured (using ldconfig,
crle, etc.) to automatically find these libraries. If the system
is not configured then the user can set LD_LIBRARY_PATH.
or
o The package should include an embedded library run-time search
path so it is not dependent on something outside of itself to work
properly.
By specifying CPPFLAGS and LDFLAGS arguments to configure, the person
who configures the package has the option to specify the flags they
like (with the drawback that she has to know about the flags).
Bob
======================================
Bob Friesenhahn
bfriesen@simple.dallas.tx.us
http://www.simplesystems.org/users/bfriesen