| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
If one of the tools that use TeX applications is generated
add the paths in /etc/paths and /etc/paths.d
version 10.5 (Leopard)
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
SK and I agree that we are surprised by that.
Both bld = env['BUILDERS']['PDF'] and bld = env['BUILDERS']['DVI'] had
lines like
bld.add_action('.tex', LaTeXAuxAction) # for DVI
bld.add_action('.tex', PDFLaTeXAuxAction) # for PDF
run from the initialization of two tools. This was a BAD thing.
That cured some test failures. For the rest I made all the TEX tests
initialize the environment with the os.environ PATH since the check
for the existence of the tools with where_is that looks on the system path.
So the tests still quietly exit if the tool is not on the system path
and now find if it is in a non-standard location like I have.
|
|
|
It now iterates until all the warnings are gone and the auxiliary files
stop changing or it hits the max retires limit.
It adds the common auxiliary files to the emitter as sideeffects
Added support for glossaries, nomenclatures, lists of figures,
lists of tables, hyperref, and beamer
The user can entry environment changes like env['TEXINPUTS'] and
they get copied to env['ENV']['TEXINPUTS'] (thanks to Dmitry Mikhin )
It also works with variantdir, duplicate =0
|
