unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mike Gran <spk121@yahoo.com>
To: guile-devel <guile-devel@gnu.org>
Subject: Minimal Guile
Date: Mon, 19 Dec 2011 12:35:21 -0800 (PST)	[thread overview]
Message-ID: <1324326921.17612.YahooMailNeo@web37905.mail.mud.yahoo.com> (raw)

Hi-

I've been keeping up with some of the discussion on other gnu lists.

One of the criticisms at the moment is that Guile is
 
1. bloated
2. hard to distribute.
 
Re point 2: hard to distribute.
 
A while ago I was looking at the idea of minimizing the number of
files needed to ship Guile as a dependency.  At the time, I thought
that one could retool the build so that it produced
- a tar.gz of the distributable header files
- libguile as a monolithic .so or .dll with no dependencies.
  Dependencies would be wrapped into the monolithic .so or .dll.
- all the compiled .go files as a tar file
- and a Guile executable that used both of the above
 
Guile and libguile would read the .go without unpacking the tar file
by using libtar.
 
There's no real advantage in this for the GNU system, but, it would
make it easier to make a distributable cross-build for non-GNU
systems.  This would make it easier to set up a download repository
of prebuilt .so, .dll, and go-lib tar files.
 
Re point 1: bloated
 
Once the infrastructure for the above is in place, one could set
up an alternate cross-build system that produced a version of
Guile that is
 
- ASCII only, "C" locale only
- Fixnum integers only
- No ability to load ltdl or ffi
- no ability to use whatever libcrypt is used for
 
This would be for the purpose of being a minimalist extension
engine.
 
What do you think?
 
-Mike Gran



             reply	other threads:[~2011-12-19 20:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-19 20:35 Mike Gran [this message]
2011-12-19 22:32 ` Minimal Guile Noah Lavine
2011-12-21 15:47   ` Andy Wingo
2011-12-21 16:03 ` Mike Gran
2011-12-21 21:05   ` Andy Wingo
2011-12-22  1:07   ` Noah Lavine
2011-12-22  8:13     ` David Kastrup
2011-12-24 15:54   ` Antono Vasiljev
2012-01-03 21:44   ` Ludovic Courtès
2012-01-03 22:53     ` Mike Gran
2012-01-03 23:25       ` Ludovic Courtès
2012-01-03 23:41         ` Mike Gran
2012-01-04  1:20       ` Mark H Weaver
2012-01-04  2:09         ` Mike Gran
2012-01-04  3:44           ` Mark H Weaver
2012-01-04 18:52             ` Mike Gran
2012-01-05  2:02               ` Mark H Weaver
2012-01-04 19:16             ` Andy Wingo
2012-01-04 20:48               ` Andreas Rottmann

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=1324326921.17612.YahooMailNeo@web37905.mail.mud.yahoo.com \
    --to=spk121@yahoo.com \
    --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).