Re: Calling .py scripts in buildscripts?

[Reinhold Kainhofer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Sonntag, 16. November 2008 schrieb Han-Wen Nienhuys:
> On Sun, Nov 16, 2008 at 2:06 PM, Reinhold Kainhofer
>
> <address@hidden> wrote:
> > I just noted that the makefiles call all python scripts directly, rather
> > than the "compiled" version in out. In particular, during the build,
> > lilypond-book or lys-to-tely will be called as:
> > python $(script-dir)/lilypond-book.py ...
> > python $(buildscript-dir)/lys-to-tely.py ...
> >
> > 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).

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?

Cheers,
Reinhold
- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, Vienna University of Technology, Austria
email: address@hidden, http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/
 * K Desktop Environment, http://www.kde.org, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFJIE+zTqjEwhXvPN0RAt7DAJ9i3GgGnO/JVjGv63XRuAu0HrPy2ACeNujT
RulsTXmcUjPdUq7PYds4D4M=
=qT31
-----END PGP SIGNATURE-----