X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fuser%2FGNUmakefile;h=a3f909f13a1f5cff0e69b43d280590dd99009cd7;hb=793925ac7c6a2cd031124beae79d2eda547d127d;hp=7e2ea57cbe108b48eadb2aeb8e2795f1fe7b393d;hpb=876ccb4004d92f3b7bd539753f8f9339b7d48490;p=lilypond.git

diff --git a/Documentation/user/GNUmakefile b/Documentation/user/GNUmakefile
index 7e2ea57cbe..a3f909f13a 100644
--- a/Documentation/user/GNUmakefile
+++ b/Documentation/user/GNUmakefile
@@ -2,43 +2,140 @@
 
 depth=../..
 
-DATA_FILES = $(wildcard *.data)
-datafiles = $(addprefix $(outdir)/,$(DATA_FILES:.data=.html))
 
-DOC_FILES = $(wildcard *.doc)
+LATEX_FILES =$(wildcard *.latex)
 
-DVI_FILES = $(addprefix $(outdir)/,$(DOC_FILES:.doc=.dvi)  $(TELY_FILES:.tely=.dvi))
+# todo: add latex.
+DVI_FILES = $(addprefix $(outdir)/, $(TELY_FILES:.tely=.dvi))
 
-EXTRA_DIST_FILES= $(DOC_FILES) $(DATA_FILES)  $(wildcard *.itexi *.itely)
+EXTRA_DIST_FILES= $(LATEX_FILES)
 
 HTML_FILES = $(addprefix $(outdir)/, $(TELY_FILES:.tely=.html))
 
-PS_FILES = $(DVI_FILES:.dvi=.ps)  $(OUTDOC_FILES:.doc=.ps) $(OUTTEX_FILES:.tex=.ps)
+PS_FILES = $(DVI_FILES:.dvi=.ps)
+PDF_FILES = $(DVI_FILES:.dvi=.pdf)
+
 PS_GZ_FILES= $(addsuffix .gz, $(PS_FILES))
 
+INFO_FILES = $(addprefix $(outdir)/, lilypond.info lilypond-internals.info)
+
 STEPMAKE_TEMPLATES=tex texinfo documentation
-LOCALSTEPMAKE_TEMPLATES=lilypond mudela
+LOCALSTEPMAKE_TEMPLATES=lilypond ly
+LILYPOND_BOOK_FLAGS=--extra-options '-e "(ly-set-option (quote internal-type-checking) \#t)"'
+
+# Hmm, what about?
+# local-dist: check-info
+
+info: #  check-info  # -> reinstate when actively hacking doco.
 
 include $(depth)/make/stepmake.make 
 
+# Ugh,ugh.
+# emacs cannot fix the menu structure when @mbinclude is used
+# lilypond.tely uses mbinclude
+TEXINFO_SOURCES := $(filter-out lilypond.tely, $(TEXINFO_SOURCES))
+
 dvi: $(DVI_FILES)
 
 ps: $(PS_FILES)
 
-# urg
-default:
 
-GENHTMLS = engraving colorado glossary computer-notation
-OUTGENHTMLS = $(addprefix $(outdir)/, $(GENHTMLS:%=%.html))
+# Cancel default info generation rule.  We want to generate info from
+# `.nexi', making sure we don't run LilyPond for inline pictures, when
+# generating info.
+$(outdir)/%.info: $(outdir)/%.texi
+
+default: 
+
+# Info is now built by default via texinfo-rules.
+# We must build them by default, otherwise they get built during make install
+info: $(INFO_FILES)
+
+
+# Generic rule using % twice not possible?
+# $(outdir)/%/%.html: $(outdir)/%.texi
+$(outdir)/lilypond/lilypond.html: $(outdir)/lilypond.texi
+	mkdir -p $(dir $@)
+	$(MAKEINFO) --output=$@ --html $<
+	-cp -f $(outdir)/*.png $(outdir)/lilypond
+	-cp -f $(outdir)/lilypond/index.html $@
+	$(deep-footify) $(shell find $(outdir)/$(*F)/*.html)
+
+$(outdir)/lilypond-internals/lilypond-internals.html: $(outdir)/lilypond-internals.texi
+	mkdir -p $(dir $@)
+	$(MAKEINFO) --output=$@ --html $<
+	-cp -f $(outdir)/*.png $(outdir)/lilypond-internals
+	-cp -f $(outdir)/lilypond-internals/index.html $@
+	$(deep-footify) $(shell find $(outdir)/$(*F)/*.html)
+
+ifeq ($(SPLITTING_MAKEINFO),yes)
+
+DEEP_HTML_FILES = $(outdir)/lilypond/lilypond.html $(outdir)/lilypond-internals/lilypond-internals.html
+
+else
+
+# Links referred to by Documentation index
+LILYPOND_LINKS=Reference-Manual.html Tutorial.html Ly2dvi.html Midi2ly.html
+
+local-WWW: deep-symlinks
+
+deep-symlinks:
+	mkdir -p $(outdir)/lilypond
+	cd $(outdir)/lilypond && $(foreach i, $(LILYPOND_LINKS),\
+		rm -f $(i) && ln -s lilypond.html $(i) &&) true
+
+endif
+
+
+local-WWW: $(HTML_FILES) $(datafiles) $(PDF_FILES) $(PS_GZ_FILES) $(DEEP_HTML_FILES) info-dir
+
+local-WWW-clean: deep-WWW-clean
+
+deep-WWW-clean:
+	rm -rf $(outdir)/lilypond $(outdir)/lilypond-internals
+
+info-dir:
+	$(SHELL) $(buildscript-dir)/install-info-html.sh --dir=$(outdir) lilypond lilypond-internals
+	$(MAKE) footify
+	$(MAKE) deep-footify
 
-local-WWW: $(HTML_FILES)   $(datafiles) $(PS_GZ_FILES)
-	$(PYTHON) $(step-bindir)/ls-latex.py --title 'User documentation' \
-	   $(DOC_FILES) $(TEX_FILES) $(TELY_FILES) \
-	  | sed "s!$(outdir)/!!g" > $(outdir)/index.html
-	$(footify) $(outdir)/index.html
 
 $(outdir)/%.bib: %.bib
 	ln -f $< $@
+# we want footers even if website builds (or is built) partly
+	$(MAKE) footify
 
-localclean:
+local-clean:
 	rm -f fonts.aux fonts.log feta*.tfm feta*.*pk 
+	rm -rf $(outdir)/lilypond $(outdir)/lilypond-internals
+
+#$(outdir)/lilypond.nexi: $(outdir)/interfaces.itexi
+#$(outdir)/lilypond.texi: $(outdir)/interfaces.itexi
+
+# Rules for the automatically generated documentation
+# When cross-compiling, we don't have lilypond, so we fake
+ifneq ($(CROSS),yes)
+
+
+# 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).
+
+$(outdir)/lilypond-internals.nexi $(outdir)/lilypond-internals.texi: $(builddir)/lily/$(outconfbase)/lilypond
+	cd $(outdir) && $(builddir)/lily/$(outconfbase)/lilypond --verbose $(abs-srcdir)/ly/generate-documentation
+	-ln $(outdir)/lilypond-internals.texi $(outdir)/lilypond-internals.nexi
+
+
+## unused
+$(outdir)/interfaces.itexi: dummy
+	cd $(outdir) && $(builddir)/lily/$(outconfbase)/lilypond $(abs-srcdir)/ly/generate-interface-doc
+
+else
+
+$(outdir)/lilypond-internals.nexi $(outdir)/lilypond-internals.texi:
+	touch $@
+	touch $(outdir)/$(*F).nexi
+
+$(outdir)/interfaces.itexi:
+	cp dummy-interfaces.itexi $@
+endif
+