This is the mail archive of the
guile@sourceware.cygnus.com
mailing list for the Guile project.
Re: Where should I install compiled modules please?
- To: richard at brainstorm dot co dot uk
- Subject: Re: Where should I install compiled modules please?
- From: Ian Grant <Ian dot Grant at cl dot cam dot ac dot uk>
- Date: Wed, 23 Feb 2000 16:15:07 +0000
- cc: guile at sourceware dot cygnus dot com
Look at guile-readline (in the subdirectory guile-readline of the guile
source) and see how it's done there: basically you install a scheme module
(which goes in the shared directory [$(datadir) in automake speak].) which
scheme module explicitly loads the C module doing something like
(dynamic-call "scm_init_readline" (dynamic-link "libguilereadline.so"))
Then libguilereadline.so is searched for on the appropriate path, which
includes the library executable directory [$(libdir) in automake speak].
In this way we don't rely on (use-modules ....) to load binary modules anymore.
This should go in the module-writers FAQ which doesn't exist.
Ian
> For support for running processes on a pseudo-terminal, I install a compiled
> module as share/guile/1.3.4/greg/libcompiled.so
>
> Obviously, as it's compiled C code, it is architecture/OS specific, and so
> should not really appear under 'share' but (in my case) under 'ix86/linux-gnu'
>
> I have tried putting it in 'ix86/linux-gnu/guile/1.3.4/greg/libcompiled.so', but
> when I do, it's not found by the guile interpreter.
>
> Is there a correct architecture/OS specific place to put this, or is my only
> option the existing location in the shared area?
>