release: 1.1.10

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

diff --git a/stepmake/stepmake/metapost-rules.make b/stepmake/stepmake/metapost-rules.make
index 302e6d757c44a2fdb97c29ea25cad6395cc3b166..4cd6423483dc3075d5cdefa3a262c2d8163c3aa4 100644 (file)
--- a/stepmake/stepmake/metapost-rules.make
+++ b/stepmake/stepmake/metapost-rules.make
@@ -4,12 +4,14 @@ $(outdir)/%.pfa: %.mf
 # 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)
-       -mp "&mfplain \mode=lowres; \mag=100.0; batchmode; input $<"
-#      -mp "&mfmp \mode=ljfour; \mag=100.0; batchmode; input $<"
-#      -mp "&mfplain modes \mode=ljfour; \mag=100.0; batchmode; \\input $<"
-#      -mp "&mfplain \mode=lowres; \mag=10.0; batchmode; input $<"
-#      -mp "&mfplain \mode=lowres; \mag=1.0; batchmode; input $<"
+       -$(METAPOST) "&mfplain \mode=lowres; \mag=100.0; batchmode; input $<"
+#      -$(METAPOST) "&mfmp \mode=ljfour; \mag=100.0; batchmode; input $<"
        $(PYTHON) $(depth)/buildscripts/ps-to-pfa.py $<
        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
+