[EMAIL PROTECTED] (Ludovic Courtès) writes: > Dan McMahill <[EMAIL PROTECTED]> writes: > >> With that I don't have to modify the guile-config output. In other >> words by default I might just get "-L/my/guile/path/lib" where I may >> actually want "-L/my/guile/path/lib -Wl,-R/my/guile/path/lib". > > Greg Troxel <[EMAIL PROTECTED]> writes: > >> Probably you are right. But not having a way to include some sort of >> rpath when needed isn't portable either. > > Doesn't Libtool solve this problem? That is, if you installed the > Libtool archive `libguile.la' and link _using Libtool_ against it, then > passing `-L/my/guile/path/lib' is enough and Libtool sets up the new > library's RPATH correspondingly. > > Granted, you don't necessarily use Libtool, and the `.la' file could be > unavailable, but that's another story...
Sure, but guile-config is documented to work for programs linking without libtool. I think guile should have a .pc file for pkg-config and guile-config should be deprecated eventually. That's really orthogonal.
pgpejbOhDr68D.pgp
Description: PGP signature
_______________________________________________ Guile-user mailing list Guile-user@gnu.org http://lists.gnu.org/mailman/listinfo/guile-user
