unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
Subject: Purpose of guile-xxx executables?
Date: 12 Sep 2002 22:12:16 +0100	[thread overview]
Message-ID: <m3znum52vj.fsf@laruns.ossau.uklinux.net> (raw)

In the last release of my guile-xlib package, I included a guile-xlib
executable that was identical to vanilla Guile except that it was
linked with my library and called scm_register_module_xxx(...) just
before scm_shell.

For the next release, I've changed to using dynamic-link and
dynamic-call, so the scm_register_module_xxx goes away.  Given this,
is there any point anymore in building the guile-xlib executable?

Two possibilities occur:

- building an executable allows me to check that my library doesn't
  contain any unresolved externals

- something to do with platforms that only perform static linking.

However, it seems to me that, on both these points, we should instead
have some more generic tool that allows the building of a custom Guile
with, in general, several libraries statically prelinked in,
e.g. Guile + libguilexlib + libguilegtk + libguilepg.

Is this correct?  If so, how should it work in detail?

        Neil



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


             reply	other threads:[~2002-09-12 21:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-12 21:12 Neil Jerram [this message]
2002-09-12 21:48 ` Purpose of guile-xxx executables? Marius Vollmer
2002-09-12 22:26 ` Rob Browning

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=m3znum52vj.fsf@laruns.ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    /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).