Re: musicxml2ly patch for articulations (fermata, staccato, accent, etc.)

[Han-Wen Nienhuys]

2007/8/19, Reinhold Kainhofer <address@hidden>:
> > > Grr, each small project has its own coding style (kdepim has spaces
> > > inside the parentheses, kdelibs has different style, lilypond another
> > > different style). That's so confusing, and I'm mainly used to the kdepim
> > > coding style, as that's my main project!
> >
> > Yes, that's unfortunate. We use the GNU coding style, FWIW.
>
> Ouch, To be honest, after looking at the style (it's at
> http://www.gnu.org/prep/standards/standards.html#Formatting, right?), I think
> it was designed to make it artificially hard to visually parse the code
> quickly.

That's what I always think when starting to work in whatever new
coding style there is, but it turns out that this is never true.

> > > Furthermore, do I really need to compile all of lilypond just to install
> > > a python script, that does not need compiling just installation?
> >
> > No, you don't have to compile anything.
> > I'm just interested in the musicxml related patches. Look under scripts/
> > and python/
>
> Yes, the scripts are there, but I still need to build lilypond, since during
> the build the preambles in musicxml2ly.py are inserted (address@hidden@
>  and @relocate-preamble@)...

you can run configure and do

  cp GNUmakefile.in GNUmakefile
  make -C python
  make -C scripts

that should suffice.

> BTW, why is TARGET_PYTHON set to /usr/bin/python instead of the
> usual "/usr/bin/env python"?\

Good question. I don't know actually.

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