This is the mail archive of the guile@cygnus.com mailing list for the guile project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: [ANN] text buffers: really alpha release


Ian Grant wrote:
> 
> There is an alternative to this, which is to use a libtool from the
> libtool CVS. This now supports building shared libraries that depend
> on other shared libraries. It can do this because most library
> formats allow for the inclusion of a search path for dependencies,
> and most link-loaders can use these sanely. However I've yet to try
> it on anything other than Linux, on which it works flawlessly.

That's not entirely true... it can't compile glib/gtk+ f'rinstance.

> If you're worried about using a CVS libtool then you could wait for
> libtool 1.3. It's due out soon, and it should include this.

The changes for full and correct inter-library dependencies are sweeping
enough to have grown a branch of their own in CVS, which we would like
to merge back in for the 1.3 release.  However if everything else is in
place before ILD, we will probably release 1.3 without it.
In that case I am determined that 1.4 will follow shortly, with working
ILD.

IIRC, it was you guys who diagnosed the problems with Gord
(then-libtool-maintainer) Matzigkeits ILD implementation... I was
wondering if you could point me at any relevant threads/archives so that
I can check things are hunky-dory in that failure mode before we release
ILD in all its glory?

Cheers,
	Gary V. Vaughan.

> 
> It seems to me this is the way to go, because it's a lot simpler: it's a
> matter of adding two switches to the libtool invocation, rather than a
> whole new shared library.
> 
> If you want a Makefile.am etc to look at then you could fetch guile-pg
> from http://www.damtp.cam.ac.uk/user/ig206/guile-pg/ It's a set of glue
> functions to link guile with a third-party shared library. It uses the new
> libtool to do this. There are also some autoconf macros in acinclude.m4
> that might be useful to you.
> 
> Another related issue is where guile modules that are in shared libraries
> should be installed. I described in an earlier message one way to resolve
> the problem of putting architecture-specific binaries under PREFIX/share
> (which is where guile looks for shared libraries that are to be loaded as
> modules.) The coding standards prohibit this, for the good-enough reason
> that the files cannot be shared across different platforms. I got around
> this by making a symlink from the shared directory to the library
> directory. The automake magic to do this is in the Makefile.am for
> guile-pg.
> 
> Have fun. "You are in a twisty maze of m4 macros, all alike .... "
> 
> Ian