Note that there are some explanatory texts on larger screens.

plurals
  1. POIs it possible to do a 'unity build' with Latex source files?
    primarykey
    data
    text
    <p>Those who know C++ may know what I mean by 'unity build':</p> <ol> <li>*.cpp files of a project are all effectively <strong>#include-ed</strong> into a single <strong>supermassive source file</strong> following <strong>#include directives</strong> specified in *.cpp and *.h files</li> <li>this source file is fed into the compiler</li> <li>finish! You get the output binary!</li> </ol> <p>Doing things this way means that there are that there are fewer intermediate files (*.o), fewer file reads and disk IO overheads, fewer invocations of the compiler, leading to a better build performance.</p> <p>My question is, is this possible <em>for Latex</em> at all? I want it because there is a <strong>slow post-processing pass</strong> that I would like to run over .tex files before building my final .pdf using pdflatex. Currently, it takes around 7 seconds to process my growing list of .tex files. I believe that running this pass over <em>one</em> file is significantly faster. This motivates my question!</p> <p>To summarize, I want to</p> <ol> <li>'<strong>merge</strong>' all the .tex files into a <strong>supermassive .tex source file</strong> by following the <strong>\input{} and \include{}</strong> macros in each .tex file</li> <li>feed the supermassive .tex source file into the <strong>slow post-processing pass</strong> (actually the Ott tex-filter, fyi)</li> <li>pipe the output straight into <em>pdflatex</em></li> <li>finish! I get the output PDF file!</li> </ol> <p>The first step is the problem here. Any ideas welcome. It's best if I don't need to write my own script to do this step!</p> <p>Many thanks!</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload