Re: [translations] again trouble with scripts

[Francisco Vila <paconet.org@xxxxxxxxx>]

2011/7/19 Federico Bruni <fedelogy@xxxxxxxxx>:
> 2011/7/19 Francisco Vila <paconet.org@xxxxxxxxx>
>>
>> 2011/7/19 Federico Bruni <fedelogy@xxxxxxxxx>:
>> > IIUC if I've already run 'make' 'make -C scripts && make -C python' will
>> > be
>> > useless.
>> > What else should I try?
>>
>> Remember that <directory> in 'make -C <directory>' is a relative path
>> from your current directory.  python/ and scripts/ are descendants of
>> the tree top, so you should only run make -C python from there.  Sorry
>> for this q'n'd, potentially pointless note.
>>
>
> Just tried and it doesn't help:
>
>
> fede@debian:~/lilypond-git/build$ make -C python
> make: Entering directory `/home/fede/lilypond-git/build/python'
> make --no-builtin-rules PACKAGE=LILYPOND package=lilypond -C auxiliar all &&
> true
> make[1]: Entering directory `/home/fede/lilypond-git/build/python/auxiliar'
> true
> make[1]: Leaving directory `/home/fede/lilypond-git/build/python/auxiliar'
> make: Leaving directory `/home/fede/lilypond-git/build/python'
> fede@debian:~/lilypond-git/build$
> fede@debian:~/lilypond-git/build$ make -C scripts
> make: Entering directory `/home/fede/lilypond-git/build/scripts'
> make --no-builtin-rules PACKAGE=LILYPOND package=lilypond -C auxiliar man
> &&  make --no-builtin-rules PACKAGE=LILYPOND package=lilypond -C build man
> && true
> make[1]: Entering directory `/home/fede/lilypond-git/build/scripts/auxiliar'
> true
> make[1]: Leaving directory `/home/fede/lilypond-git/build/scripts/auxiliar'
> make[1]: Entering directory `/home/fede/lilypond-git/build/scripts/build'
> true
> make[1]: Leaving directory `/home/fede/lilypond-git/build/scripts/build'
> make --no-builtin-rules PACKAGE=LILYPOND package=lilypond -C auxiliar all
> &&  make --no-builtin-rules PACKAGE=LILYPOND package=lilypond -C build all
> && true
> make[1]: Entering directory `/home/fede/lilypond-git/build/scripts/auxiliar'
> true
> make[1]: Leaving directory `/home/fede/lilypond-git/build/scripts/auxiliar'
> make[1]: Entering directory `/home/fede/lilypond-git/build/scripts/build'
> true
> make[1]: Leaving directory `/home/fede/lilypond-git/build/scripts/build'
> make: Leaving directory `/home/fede/lilypond-git/build/scripts'
> fede@debian:~/lilypond-git/build$
> fede@debian:~/lilypond-git/build$
> fede@debian:~/lilypond-git/build$ cd Documentation/
> fede@debian:~/lilypond-git/build/Documentation$ make ISOLANG=it
> check-translation
> ISOLANG=it /usr/bin/python
> /home/fede/lilypond-git/scripts/auxiliar/check_translation.py
> fede@debian:~/lilypond-git/build/Documentation$

I have never tried the outside-tree build, but for me, your build/
directory is only a build directory for compiling lilypond into it,
not your source directory and of course it is NOT your source tree
top.  My experience ends here but I am willing to make my first
attempt of building into build/ just to see what happens.

What if (for once) you do

  ~/lilypond-git$ ./autogen.sh
  ~/lilypond-git$ cd Documentation/
  ~/lilypond-git/Documentation$ make ISOLANG=it check-translation

for me?


-- 
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com