There are four things that should work, but, that I haven't tried out yet. You could call "dynamic-link" with the explicit pathname plus filename to your library.
If your app is a pure guile script, you could write a wrapper shell script that exports the environment variable you need and then calls the guile script. If you have a C main(), you could call lt_dladdsearchdir(const char *) from C before dlopening your library. You could wrap the function lt_dladdsearchdir as a Guile function and call it from your script. -- Mike --- Aurelien Chanudet <[EMAIL PROTECTED]> wrote: > Thank you guys for the tip. > > Unfortunately, the environnement variable set in this way doesn't > appear to be visible from the shell guile was launched from. As a > result, the environnement variable does not appear to be visible to > the dynamic link editor. > > On 7/29/05, José Roberto B. de A. Monteiro > <[EMAIL PROTECTED]> wrote: > > On Thu, Jul 28, 2005 at 05:55:59PM +0200, Aurelien Chanudet wrote: > > > Hi all, > > > > > > I have a dynamic library located in a non standard > > > place I'd like to load within guile using > > > "dynamic-link". The dynamic link editor can be told > > > where to look for the library using an environment > > > variable. Is there a way to set up the environnement > > > variable directly _from_ Guile using for instance the > > > "system" primitive ? > > > > Have you ever tried to use Guile primitive function setenv ? > > > > (setenv name value) > > > > > > > > > _______________________________________________ > Guile-user mailing list > Guile-user@gnu.org > http://lists.gnu.org/mailman/listinfo/guile-user > ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs _______________________________________________ Guile-user mailing list Guile-user@gnu.org http://lists.gnu.org/mailman/listinfo/guile-user
