PageRenderTime 80ms CodeModel.GetById 42ms app.highlight 31ms RepoModel.GetById 2ms app.codeStats 0ms

HTML | 55 lines | 55 code | 0 blank | 0 comment | 0 complexity | 6b38ccb45738898480da8f0fe3ae51b4 MD5 | raw file
 1<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "">
 2<html xmlns=""><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>6.3 Compiling multiple times</title><link rel="stylesheet" href="../latex-suite.css" type="text/css"></link><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></meta><link rel="home" href="index.html" title="Latex-Suite Reference"></link><link rel="up" href="latex-compiling.html" title="6 LaTeX Compiling"></link><link rel="prev" href="compiler-dependency.html" title="6.2 Handling dependencies in compilation"></link><link rel="next" href="compiler-output-customization.html" title="6.4 Customizing the compiler output"></link></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">6.3 Compiling multiple times</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="compiler-dependency.html">Prev</a></td><th width="60%" align="center">6 LaTeX Compiling</th><td width="20%" align="right"><a accesskey="n" href="compiler-output-customization.html">Next</a></td></tr></table><hr></hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="compiling-multiple"></a>6.3 Compiling multiple times</h3></div></div></div><p>
 3    Most LaTeX compilers need to be re-run several times in several
 4    commonly occurring situations in order to get a final camera ready copy.
 5    For example, when <code class="literal">\label</code>'s change, when new
 6    <code class="literal">\cite</code> commands are added etc. If the target format
 7    you are compiling to requires multiple compilations, then you will
 8    need to include the format in the
 9    <code class="literal">g:Tex_MultipleCompileFormats</code> setting. This is a
10    comma separated string of formats which need multiple compilations to
11    be generated correctly.
12   </p><p>
13    By default, this setting contains just the <code class="literal">dvi</code>
14    format. If you use the <code class="literal">pdflatex</code> compiler to generate
15    <code class="literal">pdf</code> files, then you might want to also include
16    <code class="literal">pdf</code> into the above setting.
17   </p><p>
18    For every format included in the
19    <code class="literal">g:Tex_MultipleCompileFormats</code> setting described
20    above, Latex-Suite will use the following logic to generate the file. Note
21    that although the following description uses <code class="literal">latex</code>
22    to refer to the compiler, it could be some other compiler such as
23    <code class="literal">pdflatex</code> for generating <code class="literal">pdf</code>
24    output.
25   </p><p>
26    </p><div class="orderedlist"><ol type="1"><li>If there was a <code class="literal">.idx</code> file, then remember
27      its contents.</li><li>Run <code class="literal">latex</code>.</li><li>If the <code class="literal">.idx</code> file changed due to the latex
28      compiler, then run <code class="literal">makeindex</code> to redo the
29      <code class="literal">.ind</code> file and then remember to rerun latex.
30     </li><li><p>
31       If the <code class="literal">.aux</code> file generated by the latex
32       compiler contains a <code class="literal">\bibdata</code> line, then it
33       means that we are using a <code class="literal">.bib</code> file. Therefore,
34       run <code class="literal">bibtex</code>.
35      </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
36        This means that we will always run <code class="literal">bibtex</code>
37        whenever we use the <code class="literal">\bibliography</code> command
38        whether or not we actually need to. At this time, Latex-Suite does not
39        parse the <code class="literal">.aux</code> file before and after the latex
40        compiler to see if we are required to rerun
41        <code class="literal">bibtex</code>.
42       </p></div></li><li>
43      If the <code class="literal">.bbl</code> file changes because of this, then
44      remember to rerun latex again.
45     </li><li>Also, we check to see if the LaTeX compiler gives certain
46      standard warnings which notify that we need to compile once again. In
47      this case also, remember to rerun LaTeX.</li><li>If we found we had to rerun latex, then we repeat
48      the steps above but not running <code class="literal">makeindex</code> or
49      <code class="literal">bibtex</code> again.</li></ol></div><p>
50   </p><p>
51    The LaTeX file is compiled atmost 5 times using this logic.  These
52    steps will ensure that on most platforms/environments, you will get a
53    clean output with all the cross-references, citations etc correctly
54    labelled and ordered. 
55   </p></div><div class="navfooter"><hr></hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="compiler-dependency.html">Prev</a></td><td width="20%" align="center"><a accesskey="u" href="latex-compiling.html">Up</a></td><td width="40%" align="right"><a accesskey="n" href="compiler-output-customization.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">6.2 Handling dependencies in compilation�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�6.4 Customizing the compiler output</td></tr></table></div></body></html>