-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Andy, On 29/11/10 21:17, Andy Wingo wrote: > On Sat 27 Nov 2010 18:42, Ian Hulin <i...@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? :)
It doesn't appear to work using 1.9.13: (PWD is /home/ian/lilypond) i...@greebo$ echo $GUILE_LOAD_COMPILED_PATH/home/ian/lilypond/scm/out i...@greebo$ ls $GUILE_LOAD_COMPILED_PATH dummy.dep i...@greebo$ guile-tools compile scm/lily-library.scm wrote `/home/ian/.cache/guile/ccache/2.0-0.S-LE-4/home/ian/lilypond/scm/lily-library.scm.go' i...@greebo$ Cheers, Ian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJM9rxEAAoJEBqidDirZqASGEMIAJnbJDLwp/Gv/ORrEnyB+rSp aG/Wa1UC6nrjcAPH2tJ8+410RGMHEDp5YWagSP37JEKBqH6sjJTpZ4cXbUaUyJCO +Fktd04uL2yr48wZzi71fjUXJOjNSe0WtJ4DqokbJ75jESj1nNLmKkTr+OJhPBvU Z18NejAWWT8Tsob8nIJfyPnfQQ7tB55aUsbjvF3VvcNCAJ59i/CS8JZ0dCHZPueW ARHbzL8raLCLBk1/A9kNUpCy8Gl5pjOkBWe4WS2QJwY6ObWyAwLUrUPeW3U4sXYB TB67DzKfNQTth7+xiB5+gQNHNLaQVSbjpaGy2Vlv9eL7p648p2OXSFULgGrKhZk= =NNrA -----END PGP SIGNATURE-----
