unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: guile-devel@gnu.org
Subject: Re: Replace ltdl with GLib's GModule
Date: Fri, 27 Mar 2020 13:01:38 +0100	[thread overview]
Message-ID: <87o8si57ml.fsf@gnu.org> (raw)
In-Reply-To: 20200324222429.GA2587085@spikycactus.com

Hello!

Mike Gran <spk121@yahoo.com> skribis:

> In a fit of pique, I pushed a new branch of Guile to the repo
> called wip-replace-ltdl-with-gmodule.  It replaces the dynamic linking
> library libltdl from libtool with the analagous library GModule
> from GLib.  It was remarkably easy, and, after a cursory test
> I was surprised to find that it seems to be working.
>
> GModule itself is a standalone library, but, I think it depends
> on GLib.  It might be possible to remove that dependency without
> much difficulty, but unfortunately, then you would be left with
> another library to maintain.

Fun!

I’m very much tired of “file not found” :-), but I don’t think Guile
should depend on GLib, which is quite big.

I think we should either fix ltdl (probably less work than porting Guile
to GModule, but also less exciting) or have a very basic wrapper around
dlopen instead of using ltdl (I think Andy had made experiments in that
direction.)

Thanks,
Ludo’.




  parent reply	other threads:[~2020-03-27 12:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200324222429.GA2587085.ref@spikycactus.com>
2020-03-24 22:24 ` Replace ltdl with GLib's GModule Mike Gran
2020-03-25  9:33   ` Duy Nguyen
2020-03-25 12:41     ` Mike Gran
2020-03-27 12:01   ` Ludovic Courtès [this message]
2020-03-27 13:27     ` Eli Zaretskii
2020-03-27 17:03       ` Mike Gran
2020-03-25 12:11 dsmich
  -- strict thread matches above, loose matches on Subject: below --
2020-03-25 14:58 dsmich

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=87o8si57ml.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@gnu.org \
    /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).