On Sun, 2007-11-11 at 09:45 -0500, Stuart Brorson wrote:
> On Sun, 11 Nov 2007, 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?
>
> Since it munges a system variable, doesn't it require root access?
No, its not a system variable. Its a hard-coded library search path
inserted in the executable at link time.
Pro:
Can build, then make install into your home-dir and run apps without
requiring setting LD_LIBRARY_PATH, e.g. from desktop launchers.
Con:
Requires relinking of libgeda, then gschem if you want to move the
executable to another location. (I'm not sure if you could still run
it using LD_LIBRARY_PATH pointing to the moved libraries though.)
--
Peter Clifton
Electrical Engineering Division,
Engineering Department,
University of Cambridge,
9, JJ Thomson Avenue,
Cambridge
CB3 0FA
Tel: +44 (0)7729 980173 - (No signal in the lab!)
_______________________________________________
geda-dev mailing list
[email protected]
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
