unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Marius Vollmer <mvo@zagadka.de>
Subject: Re: cmod-play 1 available + modsup.h additions
Date: Fri, 14 Nov 2003 15:29:11 +0100	[thread overview]
Message-ID: <871xsbf2h4.fsf@zagadka.ping.de> (raw)
In-Reply-To: <20031114082656.GE14359@powergnu.laas.fr> ( Ludovic Courtès's message of "Fri, 14 Nov 2003 09:26:58 +0100")

Ludovic Courtès <ludovic.courtes@laas.fr> writes:

> Also, will this be part of Guile 1.6.x too?

In 1.6 and going forward, 'compiled modules' are done differently.  A
'use-modules' statement, say, does not directly load a shared library.
Instead, it loads a small Scheme wrapper file that then in turn loads
the shared library via 'load-extension'.  That way, modules can depend
on one another and load each other in the same way used for Scheme
code.

A second problem is that a shared library might depend on a shared
library that is not asssociated with a module.  For example, the
module (gtk-1.2 gtk) loads libguile-gtk-1.2.so (via load-extension)
and libguile-gtk-1.2.so depends on libgtk.so which in turn depends on
libgdk.so, etc.  The (gtk-1.2 gtk) module only loads
libguile-gtk-1.2.so and the remaining libs need to be loaded
automatically.  This does indeed happen with libltdl (which is used by
Guile).

As far as I understand it, Thien's proposal does only solve the first
problem, that of modules depending on each other, but not the second
one, that of a shared library depending on another shared library that
is not used by/as a module.

The first problem does not exist in 1.6 since shared libraries are not
modules anylonger, the second one does not exist since libltdl handles
it already correctly.

( 1.6 still supports loading shared libraries as modules, but
  deprecates it. )

-- 
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user


  parent reply	other threads:[~2003-11-14 14:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-13 21:55 cmod-play 1 available + modsup.h additions Thien-Thi Nguyen
2003-11-14  8:26 ` Ludovic Courtès
2003-11-14 13:10   ` Thien-Thi Nguyen
2003-11-14 13:37     ` Ludovic Courtès
2003-11-14 17:38       ` Thien-Thi Nguyen
2003-11-14 14:29   ` Marius Vollmer [this message]
2003-11-14 14:17 ` Marius Vollmer
2003-11-14 15:28   ` Does anyone have a better scm_string_hash ? Roland Orre
2003-11-14 15:51     ` Ludovic Courtès
2003-11-17  8:33       ` Roland Orre
2003-11-17 13:01         ` Ludovic Courtès
2003-11-17 15:42         ` Marius Vollmer
2003-11-17 16:02           ` Marius Vollmer
2003-11-17 16:29             ` Marius Vollmer
2003-11-17 16:48               ` Allister MacLeod
2003-11-17 17:57                 ` Marius Vollmer
2003-11-17 19:17                   ` OT: x86 assembly timings/size (was Re: Does anyone have a better scm_string_hash ?) Allister MacLeod
2003-11-17 21:27                     ` OT: x86 assembly timings/size Marius Vollmer
2003-11-19  9:04             ` Does anyone have a better scm_string_hash ? Ludovic Courtès
2003-11-19 15:02               ` Marius Vollmer
2003-11-14 17:40   ` cmod-play 1 available + modsup.h additions Thien-Thi Nguyen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871xsbf2h4.fsf@zagadka.ping.de \
    --to=mvo@zagadka.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).