From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Diogo F. S. Ramos <diogofsr@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: Installing scheme only programs
Date: Thu, 10 Mar 2011 11:34:48 +0100 [thread overview]
Message-ID: <87sjuvw9fb.fsf@ambire.localdomain> (raw)
In-Reply-To: <20110310.035029.58396821684886596.diogofsr@gmail.com> (Diogo F. S. Ramos's message of "Thu, 10 Mar 2011 03:50:29 -0300 (BRT)")
() Diogo F. S. Ramos <diogofsr@gmail.com>
() Thu, 10 Mar 2011 03:50:29 -0300 (BRT)
I recently learn a technique where, during 'make', one 'cat' all the
sources files together, forming a big, single executable script. Doing
so, there is no need to install the .scm files, because they are all
inside the same executable file.
This is the technique used in RPX:
http://www.gnuvola.org/software/rpx/
It generalizes "compilation" from simple concatentation to include other
program-specific transforms. End result is two files to (un)install:
- $(bindir)/rpx
- $(infodir)/rpx.info
No fuss, no muss.
As for the distinction between "data" and "non-data", i tend to view anything
without the executable bit set as data, and all data as programs-in-waiting.
YMMV.
next prev parent reply other threads:[~2011-03-10 10:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 6:50 Installing scheme only programs Diogo F. S. Ramos
2011-03-10 9:57 ` Tristan Colgate-McFarlane
2011-03-10 17:42 ` Diogo F. S. Ramos
2011-03-10 10:34 ` Thien-Thi Nguyen [this message]
2011-03-10 17:46 ` Diogo F. S. Ramos
2011-03-11 2:18 ` nalaginrut
2011-03-11 4:50 ` dsmich
2011-03-11 4:57 ` Diogo F. S. Ramos
2011-03-11 5:24 ` nalaginrut
2011-03-11 9:16 ` Thien-Thi Nguyen
2011-03-11 12:53 ` Ludovic Courtès
2011-03-13 0:59 ` 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=87sjuvw9fb.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=diogofsr@gmail.com \
--cc=guile-user@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).