INFO_DOCS = lilypond lilypond-internals music-glossary lilypond-program lilypond-learning
INFO_FILES = $(INFO_DOCS:%=$(outdir)/%.info)
-TEXI2PDF_FLAGS = -I $(top-src-dir)/Documentation/user
+TEXI2PDF_FLAGS = \
+ -I $(outdir) \
+ -I $(top-src-dir)/Documentation/user \
+ -I $(top-build-dir)/Documentation/user/$(outconfbase)
ifeq ($(out),www)
INFO_IMAGES_DIR = lilypond
mkdir -p $(dir $@)
ln -sf $(depth)/.. $(@)
+ifeq ($(out),www)
local-WWW-1: $(MASTER_TEXI_FILES) $(PDF_FILES) info
local-WWW-2: $(HTML_FILES) $(DEEP_HTML_FILES) $(source-links)
+endif
$(outdir)/%.bib: %.bib
ln -f $< $@
$(outdir)/lilypond.texi $(outdir)/lilypond-program.texi $(outdir)/lilypond-learning.texi $(outdir)/music-glossary.texi: $(ITELY_FILES) $(ITEXI_FILES)
+$(outdir)/lilypond.texi: $(outdir)/ly-grammar.txt
# Rules for the automatically generated documentation
+$(outdir)/ly-grammar.txt: $(top-src-dir)/lily/parser.yy
+ cd $(outdir) && $(BISON) -v $<
+ $(auxscript-dir)/yyout2grammar.py $(outdir)/parser.output $@
+
# There used to be a dependency on a dummy target, to force a rebuild
# of lilypond-internals every time. however, this triggers
# compilation during install, which is a bad thing (tm).