Karl Hammar schreef:
What is the meaning of *.ly which point to nothing below ?
$ ls -l out/bin/
total 0
lrwxrwxrwx 1 karl users 22 May 22 17:57 *.ly -> ../../scripts/out/*.ly
lrwxrwxrwx 1 karl users 28 May 22 17:57 convert-ly ->
../../scripts/out/convert-ly
lrwxrwxrwx 1 karl users 23 May 22 17:57 lilypond -> ../../lily/out/lilypond
lrwxrwxrwx 1 karl users 31 May 22 17:57 lilypond-book ->
../../scripts/out/lilypond-book
$
Maybe it should read ln -s .../*2ly . instead of *.ly ?
If so, use attached patch.
Also note that target $(tree-share-prefix)/lilypond-force in toplevel
GNUmakefile is run before the generation of the files in scripts/out/
so any wildcard are useless in the line above, and will generate the
file *.ly instead of expanding to future files.
* GNUmakefile.in: wildcard in ln -s .../*.ly . don't work when
newly checkout'ed
thanks. applied.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for Music Notation
http://www.lilypond-design.com
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
