Hamish Moffatt wrote: > On Sun, Nov 11, 2007 at 02:02:42PM +0000, Peter Clifton wrote: >> Hi, >> >> I was thinking a bit about the need to set LD_LIBRARY_PATH for the >> common case where a user installs gEDA in their home directory. It >> represents one more barrier to getting things working, and stops users >> being able to create desktop launchers pointing directly at the >> application. (You'd need a wrapper script). >> >> It turns out that linking with libtool: >> libtool --mode=link gcc ..... >> >> will add an appropriate RPATH entry for the libraries we link with. This >> should solve the problem, and as we already (IIRC) hard-code a path to >> the GEDADATADIR in libgeda anyway. >> >> Is this a good idea? > > Sorry, I'm a few weeks behind on this list due to recent holiday. > > With regard to RPATH, Debian hates it. It prevents libraries being moved > around the search path (as specified by /etc/ld.so.conf), which is > something we have had to do before eg during the libc5 to libc6 > transition. So if possible please make use of RPATH optional. > > thanks, > Hamish
Peter, I'd suggest doing it but as part of the already existing --enable-rpath option. That way you can get the rpath stuff for people who want it and debian doesn't have to hack makefiles as part of their packaging to not use rpath. Now, personally I believe the logic is backwards and that the rpath stuff should be on by default and use --disable-rpath to turn it off, but I realize that is a personal preference. When this came up last time Ales agreed to having the rpath stuff there but disabled by default and I'm ok with that. -Dan _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
