ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Christopher Creutzig <ccr@mupad.de>
Subject: precompiling inline mp to pdf?
Date: Sat, 30 Oct 2004 22:34:06 +0200	[thread overview]
Message-ID: <4183FABE.8050402@mupad.de> (raw)

Salvete,

  for my latest project (almost done, so I don't need the answer for 
this one, but possibly in the future) I have compilation times which 
were dominated by Metapost until I switched to using --nomp most of the 
time and --automp --runs=2 whenever I changed something that results in 
changes to the Metapost stuff.  (I needed the --automp anyway, since to 
work around size limits in MetaPost I had to split the background into 
separate images, yet they had to influence one another via global 
variables -- increasing the memory limit to 80 MB made Metapost 
predictably freeze at unpredictable places in the run.)

  Now, my compile times are dominated by the mp to pdf conversion. 
Since pdf inclusion is fast (as expected), I'd like to use mptopdf once 
on each generated file and have ConTeXt include that.  Should I redefine 
\insertMPfile to first look for the pdf or is there a more clever way? 
(Note that I do want the automatic inclusion, since I'm passing the 
dimensions of external figures etc. to metapost and use the result in a 
background layer and/or as frame backgrounds.)

regards,
	Christopher Creutzig

PS: I didn't have time to analyze this when I came across it, but it 
seems that "texexec --automp file" consistently performs one TeX run too 
little.  In any case, the last thing it does is a metapost run, which 
doesn't seem sensible to me.

             reply	other threads:[~2004-10-30 20:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-30 20:34 Christopher Creutzig [this message]
2004-11-02  9:52 ` Willi Egger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4183FABE.8050402@mupad.de \
    --to=ccr@mupad.de \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).