From: Andy Wingo <wingo@pobox.com>
To: Ian Hulin <ian@hulin.org.uk>
Cc: Patrick, guile-user@gnu.org, Han-Wen Nienhuys <hanwenn@gmail.com>
Subject: Re: Generating compiled scm (.go) files as part of LilyPond build
Date: Mon, 29 Nov 2010 22:17:50 +0100 [thread overview]
Message-ID: <m3r5e3ygld.fsf@unquote.localdomain> (raw)
In-Reply-To: <4CF14302.1020502@hulin.org.uk> (Ian Hulin's message of "Sat, 27 Nov 2010 17:42:26 +0000")
On Sat 27 Nov 2010 18:42, Ian Hulin <ian@hulin.org.uk> writes:
> Our long-term aim, when we are able to move to using Guile V2.0 as an
> infrastructure, is to byte-compile as many of these as possible during
> the Lily build using something like.
> $ guile-tool compile <scm file>
> --output-file=<compiled-scm-dir><.go file>
Ralf has promised to add Guile 2.0 support to automake, so this should
be partly automated.
> At the moment, during Lily initialization we prefix the guile path
> %load-path with <lilypond-root>/scm as this is where we keep all the
> LilyPond-specific scm files.
There is also $GUILE_LOAD_COMPILED_PATH in 2.0, which you can set to the
proper path in your $builddir... which, ummm, doesn't appear to be
documented. Sorry about that. Want to patch our docs? :)
Ciao,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-11-29 21:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-27 17:42 Generating compiled scm (.go) files as part of LilyPond build Ian Hulin
2010-11-28 12:01 ` Neil Jerram
2010-11-30 18:02 ` Ian Hulin
2010-11-29 21:17 ` Andy Wingo [this message]
2010-12-01 21:21 ` Ian Hulin
2010-12-01 22:08 ` Andy Wingo
2010-12-30 11:43 ` Ian Hulin
2011-01-28 16:17 ` Andy Wingo
[not found] ` <4D433723.50501@hulin.org.uk>
2011-01-29 11:21 ` Andy Wingo
2011-07-19 13:18 ` Ian Hulin
2011-07-19 14:28 ` Andy Wingo
2011-07-19 23:08 ` Ian Hulin
2011-07-20 17:38 ` Andy Wingo
2011-07-21 12:43 ` Ludovic Courtès
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=m3r5e3ygld.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-user@gnu.org \
--cc=hanwenn@gmail.com \
--cc=ian@hulin.org.uk \
/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).