+++ /dev/null
-\version "2.11.51"
-%% +.ly: Be the first .ly file for lys-to-tely.py.
-%% Better to make lys-to-tely.py include "introduction.texi" or
-%% other .texi documents too?
-
-
-\header{
-texidoc =
-
-#(string-append "@unnumbered Introduction
-
-This document presents proofs for
-LilyPond " (lilypond-version) ". When the
-text corresponds with the shown notation, we consider LilyPond Officially
-BugFree (tm). This document is intended for finding bugs and for
-documenting bugfixes.
-
-In the web version of this document, you can click on the file name
-or figure for each example to see the corresponding input file.
-
-TODO: order of tests (file names!), test only one feature per test.
-Smaller and neater tests.
-")
-
-}
-
-%
-% make sure the .png is generated.
-%
-\lyrics { "(left blank intentionally)" }
-
--- /dev/null
+@unnumbered Introduction
+
+This document presents proofs for
+LilyPond @lilypondversion). When the
+text corresponds with the shown notation, we consider LilyPond Officially
+BugFree (tm). This document is intended for finding bugs and for
+documenting bugfixes.
+
+In the web version of this document, you can click on the file name
+or figure for each example to see the corresponding input file.
+
+TODO: order of tests (file names!), test only one feature per test.
+Smaller and neater tests.
+
+@unnumbered Regression test cases
+
--- /dev/null
+@unnumberedsec Introduction
+
+This document presents proofs for the musicxml2ly script provided with
+LilyPond @lilypondversion. The files don't have a description yet, so
+there is no official indication when the output is wrong.
+These snippets are provided as unit test files in MusicXML, converted to
+a .ly file by musicxml2ly and then processed by lilypond as usual.
+
+If something does not seem wright in the output, it might either be that this
+feature has not been implemented yet, has been wrongly implemented, or a regression
+has crept in recently...
+This document is intended for finding bugs and for documenting bugfixes.
+
+In the web version of this document, you can click on the file name
+or figure for each example to see the corresponding .ly intermediary file.
+
+TODO: Find a way to add a description to the .ly files for texinfo.
+
+The files are categorized by their first two digits with the following meaning:
+@itemize
+@item 00 ... Basics: Pitches, durations, rests, clefs, keys, time sigs, ties, etc.
+@item 01 ... Chords
+@item 02 ... MusicXML notations and articulations (articulations, ornaments, technicals, text markup)
+@item 03 ... MusicXML directions (dynamics; single symbols, not spanners like hairpins)
+@item 04 ... Spanners (hairpin, octave shift, trill, glissando, etc.)
+@item 05 ... Header information (title, composer, poet, etc.)
+@item 06 ... Lyrics
+@item 08 ... Multiple parts (staves)
+@item 09 ... Measure issues: Repeats, barlines, pickup measures, mid-measure barlines/repeats
+@item 10 ... Multiple voices per staff
+@item 12 ... Triplets, Tuplets
+@item 13 ... Grace notes
+@item 14 ... Multi-staff parts (one voice on multiple staves, e.g. PianoStaff)
+@item 15 ... Percussion
+@item 17 ... Guitar notation: Chord names, Fretboards, Tablature notation
+@item 18 ... Figured bass
+@item 19 ... Page layout: font/paper size, margins, spacing
+@item 20 ... Compressed MusicXML files
+@item 99 ... Compatibility modes with broken MusicXML exporters (i.e. ignore beams for Sibelius 5)
+@end itemize
+++ /dev/null
-\version "2.10.0"
-%% +.ly: Be the first .ly file for lys-to-tely.py.
-%% Better to make lys-to-tely.py include "introduction.texi" or
-%% other .texi documents too?
-
-
-\header{
-texidoc =
-
-#(string-append "@unnumbered MusicXML regression and coverage test
-
-This document presents proofs for the musicxml2ly script provided with
-LilyPond " (lilypond-version) ". The files don't have a description yet, so
-there is no official indication when the output is wrong.
-These snippets are provided as unit test files in MusicXML, converted to
-a .ly file by musicxml2ly and then processed by lilypond as usual.
-
-If something does not seem wright in the output, it might either be that this
-feature has not been implemented yet, has been wrongly implemented, or a regression
-has crept in recently...
-This document is intended for finding bugs and for documenting bugfixes.
-
-In the web version of this document, you can click on the file name
-or figure for each example to see the corresponding .ly intermediary file.
-
-TODO: Find a way to add a description to the .ly files for texinfo.
-
-The files are categorized by their first two digits with the following meaning:
-@itemize
-@item 00 ... Basics: Pitches, durations, rests, clefs, keys, time sigs, ties, etc.
-@item 01 ... Chords
-@item 02 ... MusicXML notations and articulations (articulations, ornaments, technicals, text markup)
-@item 03 ... MusicXML directions (dynamics; single symbols, not spanners like hairpins)
-@item 04 ... Spanners (hairpin, octave shift, trill, glissando, etc.)
-@item 05 ... Header information (title, composer, poet, etc.)
-@item 06 ... Lyrics
-@item 08 ... Multiple parts (staves)
-@item 09 ... Measure issues: Repeats, barlines, pickup measures, mid-measure barlines/repeats
-@item 10 ... Multiple voices per staff
-@item 12 ... Triplets, Tuplets
-@item 13 ... Grace notes
-@item 14 ... Multi-staff parts (one voice on multiple staves, e.g. PianoStaff)
-@item 15 ... Percussion
-@item 17 ... Guitar notation: Chord names, Fretboards, Tablature notation
-@item 18 ... Figured bass
-@item 19 ... Page layout: font/paper size, margins, spacing
-@item 20 ... Compressed MusicXML files
-@item 99 ... Compatibility modes with broken MusicXML exporters (i.e. ignore beams for Sibelius 5)
-@end itemize
-")
-
-}
-
-%
-% make sure the .png is generated.
-%
-\lyrics { "(left blank intentionally)" }
\ No newline at end of file
TITLE=Lilypond musicxml2ly Regression Tests
-ILY_FILES = $(call src-wildcard,*.ily)
-EXTRA_OUT_LY_FILES = ${ILY_FILES:%.ily=$(outdir)/%.ly}
-EXTRA_DIST_FILES += $(ILY_FILES)
+OUT_ITEXI_FILES = ${ITEXI_FILES:%.itexi=$(outdir)/%.itexi}
-ITEXI_FILES = $(call src-wildcard,*.itexi)
-EXTRA_OUT_LY_FILES = ${ITEXI_FILES:%.itexi=$(outdir)/%.itexi}
-EXTRA_DIST_FILES += $(ITEXI_FILES)
+COLLATED_FILES = $(sort $(OUT_LY_FILES) $(OUT_ITEXI_FILES) )
include $(depth)/make/stepmake.make
TITLE=Lilypond musicxml2ly Regression Tests
-.SUFFIXES: .ily
-$(outdir)/%.ly: %.ily
- ln -f $< $@
-
$(outdir)/%.itexi: %.itexi
ln -f $< $@
-$(outdir)/collated-files.tely: $(LY_FILES) $(OUT_LY_FILES)
+$(outdir)/collated-files.tely: $(COLLATED_FILES)
$(PYTHON) $(LYS_TO_TELY) --name=$(outdir)/collated-files.tely --title="$(TITLE)" $^
TITLE=LYs Doc
+
+ifeq ($(COLLATED_FILES),)
+COLLATED_FILES = $(sort $(TEXINFO_SOURCES) $(LY_FILES) $(OUT_LY_FILES) )
+endif
MUSICXML_FILES = $(call src-wildcard,*.xml)
MUSICMXL_FILES = $(call src-wildcard,*.mxl) # Allow .mxl for compressed files
-OUT_LY_FILES = $(sort ${MUSICXML_FILES:%.xml=$(outdir)/%.ly} ${MUSICMXL_FILES:%.mxl=$(outdir)/%.ly} ${EXTRA_OUT_LY_FILES})
+OUT_LY_FILES = $(sort ${MUSICXML_FILES:%.xml=$(outdir)/%.ly} ${MUSICMXL_FILES:%.mxl=$(outdir)/%.ly})
OUT_FILES = $(OUT_LY_FILES)
EXTRA_DIST_FILES += $(MUSICXML_FILES) $(MUSICMXL_FILES)
projects / lilypond.git / commitdiff