This is the mail archive of the
guile@cygnus.com
mailing list for the Guile project.
Re: C modules and shared libraries
Ian Grant <I.A.N.Grant@damtp.cam.ac.uk> writes:
> The present module system works for C modules when the module
> doesn't need any other shared libraries that aren't already loaded
> with guile. However, if a C module does depend on another shared
> library then it won't load.
I feel like I must say something about this, although it will probably
not be very helpful.
The current situation about dynamic linking is not the best one. The
libtool people are working on it, and I think we should use their
stuff. I don't think we should build our own dynamic-linking
abstraction.
The dynamic linking code in guile-gtk is only a kluge until libtool
works good enough. It already does on GNU/Linux, I think. Libtool is
close enough (or already) there, that I don't think we should install
the guile-gtk code in Guile.
The only think we should do with Guile at this moment is to beef up
the dynmic-link function so that the libguiledlopenhelper kluges are
no longer necessary. What about extending dynamic-link to take a
":global BOOL" keyword argument? ":global TRUE" would be the default.
I'll implement that when nobody objects.
- Marius