epstopdf problem

Prev

Newsgroups: comp.text.tex

> epstopdf is a _program_ not a package :-)
> Use it to convert your .eps files to .pdf files, before pdflatex-ing
> them. Don't use file extensions in the \includegraphics:
>
> \includegraphics{myfile}
>
> will use myfile.eps when you convert to PostScript, and myfile.pdf
> when you use pdflatex to get a PDF. (The latter also accepts .png and
> .jpeg.)

epstopdf is both a program AND a package, the latter written by Heiko Oberdiek. From the documentation:

% Function: This packages adds support of handling eps images % to package graphic{s,x} with option `pdftex'. % If an eps image is detected, epstopdf is automatically % called to convert it to pdf format.

epstopdf problem

> Since epstopdf is also a program, one solution to your problem would be
> to run it in advance.  In bash,
>
> for file in *.eps
> do
>   epstopdf $file $(file%eps}.pdf
> done
>
> Run this once before you start, and then you can omit the epstopdf
> package and not have to make repeated runs through your document.

There will be no repeated runs with the epstopdf package, if the extension is omitted. A Makefile would make more sense, because then epstopdf will only called if necessary.

Heiko

epstopdf problem

> > A Makefile would make more
> > sense, because then epstopdf will only called if necessary.
>
> True, except that then he has to maintain the makefile by keeping a
> complete list of all the source files.

With GNU make this is possible with few lines in the Makefile:

# collect all .eps files in current directory:
images := $(wildcard *.eps)

# replace ".eps" file extension with ".pdf":
images := $(patsubst %.eps,%.pdf,$(images))

# implicite rule that calls epstopdf:
%.pdf : %.eps
        epstopdf $<

# main rule for the project, for example:
all: test.tex $(images)
        pdfelatex $<

Heiko