+2002-06-12 Jan Nieuwenhuizen <janneke@gnu.org>
+
+ * stepmake/stepmake/generic-vars.make:
+ * make/lilypond-vars.make:
+ * GNUmakefile.in (builddir-setup): New setup for builddir run.
+ Fixes LilyPond run from builddir for --srcdir builds.
+
+ * Documentation/windows/GNUmakefile (OUT_PROFILES): Bugfix for
+ --srcdir build.
+
2002-06-12 Han-Wen <hanwen@cs.uu.nl>
* scm/grob-description.scm (all-grob-descriptions): add
chmod 755 $@
# Urg
-$(outdir)/lilypond-profile.sh: $(outdir)/../$(depth)/buildscripts/out/lilypond-profile
+$(outdir)/lilypond-profile.sh: $(outdir)/../$(depth)/buildscripts/$(outconfbase)/lilypond-profile
cp $< $@
chmod 755 $@
fonts:
$(MAKE) -C $(depth)/mf
-doc: lily fonts
+run-reqs: builddir-setup fonts lily
+web-reqs: run-reqs pfa-fonts
+
+doc: run-reqs
$(MAKE) -C Documentation
-web-doc: pfa-fonts
+web-doc: web-reqs
$(MAKE) out=www -C Documentation WWW
$(MAKE) footify
TOP_HTMLS = index.html short-examples.html long-examples.html
-short-examples: pfa-fonts
+short-examples: web-reqs
$(MAKE) out=www -C input WWW
$(PYTHON) $(buildscript-dir)/mutopia-index.py -o short-examples.html input/
-long-examples: pfa-fonts
+long-examples: web-reqs
$(MAKE) out=www -C mutopia WWW
$(PYTHON) $(buildscript-dir)/mutopia-index.py -o long-examples.html mutopia/
lily/$(outdir)/lilypond:
$(MAKE) -C lily
-local-web: fontpaths fonts lily $(TOP_HTMLS:%.html=%) footify do-top-doc top-web
+local-web: web-doc $(TOP_HTMLS:%.html=%) footify do-top-doc top-web
top-web:
cd $(builddir) && rm -f `find . -name \*.html~ -print`
#WWW: local-WWW
-html-doc: local-web
web: local-web
-index: local-web
+html-doc: web
+index: web
local-WWW-clean: top-WWW-clean
rm -f $(TOP_HTMLS) lily-[0-9]*.png
$(SHELL) $(buildscript-dir)/clean-fonts.sh
-
-
WWW:
-fontpaths:
- -ln -s $(depth)/mf/out dvips
- -mkdir -p fonts
- -rm fonts/source
- -ln -s ../$(depth)/mf fonts/source
- -ln -s ../$(depth)/mf/out fonts/afm
- -ln -s ../$(depth)/mf/out fonts/tfm
- -ln -s ../$(depth)/mf/out fonts/type1
+default: builddir-setup
+
+builddir-setup: $(depth)/$(builddir)/share/lilypond/$(TOPLEVEL_VERSION)-force
+
+$(depth)/$(builddir)/share/lilypond/$(TOPLEVEL_VERSION)-force:
+ # Preparing LilyPond tree for builddir exec
+ @cd $(depth)/$(builddir) && rm -rf share
+ @cd $(depth)/$(builddir) && mkdir -p share/lilypond
+ @cd $(depth)/$(builddir)/share/lilypond && mkdir -p $(TOPLEVEL_VERSION)
+ @cd $(depth)/$(builddir)/share/lilypond/$(TOPLEVEL_VERSION) && \
+ ln -s ../../../$(srcdir)/ly ly && \
+ ln -s ../../../mf/$(outconfbase) dvips && \
+ ln -s ../../../mf/$(outconfbase) afm && \
+ ln -s ../../../mf/$(outconfbase) tfm && \
+ ln -s ../../../$(srcdir)/mf && \
+ ln -s ../../../$(srcdir)/ps && \
+ ln -s ../../../$(srcdir)/scm && \
+ ln -s ../../../$(srcdir)/tex
+ @cd $(depth)/$(builddir)/share/lilypond/$(TOPLEVEL_VERSION) && \
+ mkdir fonts
+ @cd $(depth)/$(builddir)/share/lilypond/$(TOPLEVEL_VERSION)/fonts && \
+ ln -s ../../../../$(srcdir)/mf source && \
+ ln -s ../../../../mf/$(outconfbase) afm && \
+ ln -s ../../../../mf/$(outconfbase) tfm && \
+ ln -s ../../../../mf/$(outconfbase) type1
MAJOR_VERSION=1
MINOR_VERSION=5
PATCH_LEVEL=60
-MY_PATCH_LEVEL=mb1
+MY_PATCH_LEVEL=jcn1
# use the above to send patches: MY_PATCH_LEVEL is always empty for a
# released version.
## settings to run LilyPond
-export PATH:=$(topdir)/lily/out:$(topdir)/buildscripts/out:$(PATH)
-export TEXMF:={$(topdir),$(shell kpsexpand \$$TEXMF)}
+export PATH:=$(abs-builddir)/lily/$(outconfbase):$(abs-builddir)/buildscripts/$(outconfbase):$(PATH)
+
+# LilyPond is often run from within $(outdir), making a relative
+# PREFIX incorrect.
+export LILYPONDPREFIX:=$(shell cd $(depth)/$(builddir)/share/lilypond/$(TOPLEVEL_VERSION); pwd)
+
+export PYTHONPATH:=$(topdir)/python:$(PYTHONPATH)
+
+## arg, TEXINPUTS, TFMFONTS, MFINPUTS may still override and thus break this
+export TEXMF:={$(LILYPONDPREFIX),$(shell kpsexpand \$$TEXMF)}
+
+export MFINPUTS:=
+export TEXINPUTS:=
+export TFMFONTS:=
+
export extra_mem_top=1000000
export extra_mem_bottom=1000000
export DVIPSMAKEPK := mktexpk --destdir $(topdir)/mf/out
endif
-# don't change to "depth". It makes the GUILE barf.
-#
-# LilyPond is often run from within $(outdir), making a relative
-# PREFIX incorrect.
-export LILYPONDPREFIX:=$(shell cd $(depth)/ ; pwd)
-
-export PYTHONPATH:=$(topdir)/python:$(PYTHONPATH)
# guile load path?
ABC2LY = $(script-dir)/abc2ly.py
CONVERT_LY = $(script-dir)/convert-ly.py
-LILYPOND = $(depth)/$(builddir)/lily/$(outconfbase)/lilypond
+LILYPOND = $(abs-builddir)/lily/$(outconfbase)/lilypond
LILYPOND_BOOK = $(script-dir)/lilypond-book.py
-LILYPOND_BOOK_INCLUDES = -I $(pwd) -I $(outdir) -I$(input-dir) -I $(input-dir)/tricks/ -I $(input-dir)/regression/ -I $(input-dir)/test/ -I $(input-dir)/tutorial/ -I $(depth)/$(builddir)/mf/$(outconfbase)/ -I $(depth)/$(builddir)/mf/out/
+LILYPOND_BOOK_INCLUDES = -I $(pwd) -I $(outdir) -I$(input-dir) -I $(input-dir)/tricks/ -I $(input-dir)/regression/ -I $(input-dir)/test/ -I $(input-dir)/tutorial/ -I $(abs-builddir)/mf/$(outconfbase)/ -I $(abs-builddir)/mf/out/
LY2DVI = $(script-dir)/ly2dvi.py
LYS_TO_TELY = $(buildscript-dir)/lys-to-tely.py
PS_TO_GIFS = $(buildscript-dir)/ps-to-gifs.sh
DEPTH = $(depth)/$(package-depth)
ifeq ($(topdir),)
-topdir := $(shell cd $(depth); pwd)
+abs-srcdir := $(shell cd $(depth); pwd)
+#deprecated
+topdir := $(abs-srcdir)
+abs-builddir := $(shell cd $(depth)/$(builddir); pwd)
endif
pwd := $(shell pwd)