On Sat, Apr 12, 2008 at 01:58:12PM +0100, Ben Hutchings wrote: > On Sat, 2008-04-12 at 08:30 +0200, Mike Hommey wrote: > > On Sat, Apr 12, 2008 at 01:40:29AM +0100, Ben Hutchings wrote: > > > Package: xulrunner-dev-static > > > Version: 1.9~b4-1 > > > Severity: normal > > > > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA1 > > > > > > The library flags in libxul.pc and libxul-unstable.pc are: > > > > > > - -L/usr/lib/xulrunner-devel-1.9/lib -lxpcomglue_s -lxul -lxpcom > > > > > > libxul.so and libxpcom.so are installed in /usr/lib/xulrunner-1.9 so > > > these flags will result in executables that cannot be loaded unless > > > that directory is added to the library search using the -rpath linker > > > option or LD_LIBRARY_PATH. > > > > I think it's not the .pc file role to enforce the use or rpath or > > LD_LIBRARY_PATH. > <snip> > > It's supposed to specify the linker flags you need to get a working > executable. Now mozilla-dev and libxul-dev never did this either, but > it's about time this was fixed.
The libxul and libxul-unstable pc files are ment for dependent glue components. You use that for any component that gets loaded into an already booted up xpcom environment (like plugins, extensions and components). For those a -rpath is obvioulsly not required (nor wanted). Standalone apps - like mike pointed out - need to use the -embedding pc files and start xpcom explicitly like i showed in the other post. - Alexander -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
