Re: evo and firefox revisited...

["Joseph E. Sacco, PhD" <joseph_sacco comcast net>]

For some applications, for example epiphany, libtool uses the linker
directives, -R or -rpath, to set runtime library search paths. Other
applications do not. 

It would appear that specifying a runtime library search path is a GNOME
coding standards issue. 

I would think that specifying runtime library search path(s) is a good
idea since the specification of such is only a "suggestion" that can be
overridden by suing environment variables.


-Joseph

===============================================================================

On Mon, 2005-07-25 at 21:31 -0400, Carson Gaspar wrote:
> --On Monday, July 25, 2005 9:25 PM -0400 "Joseph E. Sacco, PhD" 
> <joseph_sacco comcast net> wrote:
> 
> > That is an interesting approach.  Since "we" have the ability to patch
> > things at various stages of a build ,pre-fetch to post-install, the .pc
> > files could be "tweaked" as we choose.
> >
> >> From your experiences, which packages might be good candidates for .pc
> > file modification?
> 
> Last I checked, all of them that include -L arguments. _None_ of them set 
> rpath. I just grep'd for '-L' in the pkgconfig dirs and used a simple perl 
> script to modify them. That was a while ago, though - it was so much work I 
> just changed my build env to set LD_RUN_PATH, which (on Solaris) Just Works.
> 
> But then I'm a firm believer that $LD_LIBRARY_PATH is Evil.
> 
> -- 
> Carson
> 
-- 
joseph_sacco [at] comcast [dot] net
-- 
joseph_sacco [at] comcast [dot] net