Re: problem with texexec and inline metapost

[Taco Hoekwater <bittext@quicknet.nl>]

Eckhart Guthöhrlein wrote:
> 
> At 08:47 04.07.2001 +0200, Hans Hagen wrote:
> >At 08:01 PM 7/3/01 +0200, Eckhart Guthöhrlein wrote:
> > >When running texexec over my input file containing a metapost graphic
> > >(first time, no mpgraph files exist), metapost is called after the first
> > >run, but then tex is not called again. Therefore, I have to call texexec
> > >twice to actually get the graphics in my dvi file. Accordingly, changes to
> > >the mp code become effective only after the second call to texexec (when
> > >creating pdf. - the dvi driver of course finds the updated file after the
> > >first run). I thought texexec would do this job for me, so perhaps there is
> > >a switch I didn't see yet?
> 
> ...
> 
> >
> >What latest? The ones i uploaded the last few days *do* an extra pass with
> >external mp graphics {based on checksum calculation] but only with the
> >undocumented --automprun, so
> >
> >texexec --automprun yourfile.tex
> 
> Runtime graphics with \write18 are compiled each tex run, no matter if they
> were changed or not. A checksum calculation could speed up things
> significantly. Perhaps this is a feature worth thinking of, if it can be
> implemented with acceptable effort.

You need checksum calculation in TeX macros then, since nothing else is
called
inbetween. Possible, of course, but it might actually be slower than
calling MP
regardless of change.

Greetings, Taco