Re: Generating compiled scm (.go) files as part of LilyPond build

[Ludovic Courtès]

Hi Ian,

Ian Hulin <address@hidden> skribis:

> On Tue 19 Jul 2011 15:28:41 BST, Andy Wingo wrote:

>> On Tue 19 Jul 2011 15:18, Ian Hulin <address@hidden> writes:

>>> The problem is knowing where the cache is. For Lilypond, we need to
>>> have a common root directory off of which we can hang the compiled
>>> files in scm/out.
>>
>> Why do you care?  (Honest question.)
>>
> (Honest answer)
> Because if Lilypond is run up with the Guile default of --auto-compile
> it will check for and generate compiled files in a different place to
> where we want to have produced them at build-time.

Would it work for you to have makefile rules to build/install .go files
where you want?

For Automake, something like this:
<http://git.savannah.gnu.org/cgit/guile-rpc.git/tree/modules/Makefile.am#n86>.

Thanks,
Ludo’.