unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
* Purpose of guile-xxx executables?
@ 2002-09-12 21:12 Neil Jerram
  2002-09-12 21:48 ` Marius Vollmer
  2002-09-12 22:26 ` Rob Browning
  0 siblings, 2 replies; 3+ messages in thread
From: Neil Jerram @ 2002-09-12 21:12 UTC (permalink / 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


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2002-09-12 22:26 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-09-12 21:12 Purpose of guile-xxx executables? Neil Jerram
2002-09-12 21:48 ` Marius Vollmer
2002-09-12 22:26 ` Rob Browning

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).