- You must then use latex and dvipdf in order to compile the file, rather than just pdflatex.
- It lacks modularity. This is particularly problematic when you are not completely sure what the finished graph should look like. I often create a graph, decide to try something else, comment out all or part of the graph and make my changes. This results in a lot of commented-out code, particularly if I add comments to explain what differentiates one graph from another. It would be cleaner to create a graphic with a descriptive name and include that descriptively-named graphic in a file. Then, even if I decide to try something different, I can simply create a second graphic, and my text file remains much cleaner.
- create the graphic normally as you would any in any pdf file
- produce the pdf file. It will be a full-size page with excess white space.
- crop the excess white space.
- include the cropped output file in your destination file.
Follow the steps in my previous post. You'll now have a tex file. You don't want page numbers, so make sure the preamble includes the following command:
2. Produce the pdf file. It will be a full-size page with excess white space.
You can't use pdflatex with pstricks; instead use
This will produce the output example.pdf. It's a full-size page including excess white space.
3. Crop the excess white space.
will create the output file example-crop.pdf.
4. Include the cropped output file in your destination file.
First, add to the preamble
5. Compile your final file. Unless something else is preventing you, you can now use pdflatex to compile the final file.
You should now have created a dependency graph as a stand-alone file, and included it in a separate pdf file! It took me a long time to get all these steps. I was stuck on trying to use dvipng, which I was not able to get to recognize the arcs in the dependency graph. So I hope this prevents someone else from having the same trouble!