Re: Calling .py scripts in buildscripts?

[Han-Wen Nienhuys]

On Sun, Nov 16, 2008 at 2:51 PM, Reinhold Kainhofer
<address@hidden> wrote:

>> > Is there any particular reason, why we can't call the compiled versions
>> > $(script-dir)/out/lilypond-book and $(buildscript-dir)/out/lys-to-tely?
>> > My
>>
>> it complicates development a bit as changes in the .py script don't
>> apply to creating the docs unless you compile first.
>
> Ah, okay. From musicxml2ly development I'm used to that anyway, since the
> musicxml.py, musicexp.py and lilylib.py packages need to be compiled to the
> out/ directory in any case.
>

> One problem is that my patch for @lilypondversion in lilypond-book does not
> work for building the docs with the .py scripts (since program_version is
> @TOPLEVEL_VERSION@ in the .py files, the @lilypondversion will be replaced by
> @TOPLEVEL_VESION@ in the .texi file and will not compile).

Yeah; feel free to do something sensible for this.  You could strip
out @s from the version string as a bare minimum.

> I also noticed that of course convert-ly will not work this way. But then, the
> only time convert-ly is called in the makefiles is in make/ly-targets.make:
> local-convert-ly:
>        $(PYTHON) $(CONVERT_LY) --edit --assume-old *ly
> As you can see, that call is apparently never called, because the --asume-old
> option doesn't even exist any more... Shouldn't this target be either updated
> or removed?

Yep. Go ahead!


-- 
Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen