3 Answers
3

The easiest way is running xelatex instead of pdflatex. It detects itself PostScript code or eps images in the document and does the conversion on the fly. If you do not want to use xelatex then there are other solutions:

If you have an up-to-date TeX distribution use

\usepackage[pdf]{pstricks}

and then run your document with pdflatex -shell-escape <file>. Then the PSTricks images are created on-the-fly as stand alone pdf images and saved in <file>-pics.pdf. If you have an older system use

For Windows you have to install a Perl version, if you want to use the full power of the auto-pst-pdf package. However, if you do not want or cannot install Perl then use

\usepackage[crop=off]{auto-pst-pdf}

There is also a Perl script pst2pdf which can create the document with pdflatex and also the PSTricks images as pdf|png|whatever images. It takes the preamble of the main document and creates stand-alone-documents for all PostScript specific code.

I'd not seen this new option: worth knowing about.
–
Joseph Wright♦Jan 6 '11 at 19:43

1

I see one shortcoming with pstricks and tikz (mentioned several times by other users): this is the fact that we have to compile over and over the same figures when working on a report. With the shell escape, it becomes problematic because the compilation takes longer. Would it be difficult to implement a test so that if the <file>-pics.pdf already exists, latex skips the compilation of the associated pstricks code? Equivalently, it may be more relevant to compile the pstricks figures separately (separate files) and then, input the pic.pdf only in the main file. Any thoughts?
–
plutonJan 6 '11 at 19:58

@pluton: for TikZ/pgf you can use the externalise library to do this. I've just been using it on a very picture-intensive document (116 separate pictures) and it saved a lot of hanging around waiting for the thing to compile.
–
Loop SpaceJan 6 '11 at 20:20

If you copy and paste this makefile to one of yours make sure to put the tabs at the right locations.

An advantage of this approach is that it works smoothly, just typing make after editing your LaTeX files will make all the hard work for you with no other intermediate steps for you to take care of. If you have to process bib references then type: make, then bibtex and make again.

How about if you are not using a command line or for that much linux at all?
–
night owlDec 11 '11 at 8:07

I use winedt 7/8. But i don´t know i have to do for make (LATEX + DVI + PS + PDF). I don´t see that option in WinEdt. I don´t know where y must COPY & PASTE the previous text of Carlos Linares.
–
Mika IkeJun 9 '13 at 12:41