Re: Issue 1055 in lilypond: guile 2.0

[lilypond]

Comment #19 on issue 1055 by address@hidden: guile 2.0
http://code.google.com/p/lilypond/issues/detail?id=1055

Another thing to think of when we move to Guile 2.0.  At the moment we have  
been relying in on Guile AUTOCOMPILE to create .go files on-the-fly in a  
private Guile directory.

This means that we are compiling scm/*.scm files as and when they are  
referenced in lily.scm.  Guile itself compiles its scm files as part of its  
build using
guile-tools compile.  There is an interface for this nin the Guile  
repl ,compile-file, but there is currently nothing we can call from within  
a .scm file, so we can't tweak ly:load or write a similar procedure to do  
the compile the .go for us dynamically if it doesn't already exist,

If we do need to compile .scm files during the build }}shudder{{, where  
would be write the .go files, out/scm?  I.e. scm/lily-library.scm compiles  
to out/scm/lily-library.go, or would we do as the guile build does and put  
the .go files into the source directory scm/lily-library.scm ->  
scm/lily-library.go?

I'm thinking about this as we already need to revise the load order to fix  
T1349.

Cheers

Ian

Cheers,
Ian