release: 1.3.76

[lilypond.git] / stepmake / stepmake / metapost-rules.make

diff --git a/stepmake/stepmake/metapost-rules.make b/stepmake/stepmake/metapost-rules.make
index 8c73b296e0fd073159ed806b76f9c746ced9d5df..6e135ede159b64e20210a80e711fd5ba4a35e7d6 100644 (file)
--- a/stepmake/stepmake/metapost-rules.make
+++ b/stepmake/stepmake/metapost-rules.make
@@ -1,27 +1,15 @@
 
-# urg
-# i've got no idea what this scaling could be for, on both sides...
-# it seems that 'low_res', which should be all we ever need according
-# to the metapost mfplain guru, really does 200dpi, iso 600dpi (minimun)
-#      -$(METAPOST) "&mfmp \mode=ljfour; \mag=100.0; batchmode; input $<"
-#      -$(METAPOST) "&mfplain \mode=lowres; \mag=100.0; batchmode; input $<"
+# Don't remove $(outdir)/.log's.  Logs are a target!
 
-$(outdir)/%.0: %.mf mfplain.mem  
-       -$(METAPOST) "&mfplain \mode=lowres; \mag=1.0; nonstopmode; input $<"
-
-
-
-mfplain.mem: mfplain.ini
-       $(INIMETAPOST) mfplain.ini
+$(outdir)/%.0: %.mf $(outdir)/mfplain.mem  
+       -$(METAPOST) "&$(outdir)/mfplain \mode=lowres; \mag=1.0; nonstopmode; input $<"
 
+$(outdir)/mfplain.mem: $(MFPLAIN_MP)
+       $(INIMETAPOST)  $(INIMETAPOST_FLAGS) $(MFPLAIN_MP) dump
+       mv mfplain.* $(outdir)
 
 $(outdir)/%.pfa: $(outdir)/%.0
        $(PYTHON) $(depth)/buildscripts/ps-to-pfa.py --output $(basename $<).pfa $<
        rm -f $(basename $(@F)).[0-9]*
-       rm -f $(basename $<).log $(basename $<).tfm
-
-
-
-#dokkum:~/usr/src/lilypond/mf$ inimpost /usr/share/texmf/metapost/base/mfplain.mp
-#[....] \dump
+       rm -f $(basename $(@F)).tfm $(basename $(@F)).log