| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
On a linux host (missing some things that may be on the Travis CI
setup), Py3.8a3 now shows 19 fails, 1048 pass, with 84 Warning: messages.
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| |
|
|
|
|
| |
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)
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
from .eps files for the pdf latex builder
That is if the .tex file has "\includegraphics{figure1}"
and the file figure1.eps then when using the .DVI builder
latex will find the file and all is fine.
However, when using the .PDF builder pdflatex can not
process .eps files and will fail.
After this patch the user will need to add
env.PDF('figure1.eps')
Update two tests that used the old feature and would fail otherwise
I could not come up with a way to test for a feature
that is removed. That is, I can write a test that works
before the update and fails after but not the other way around.
|
|
|
latex document for commands that affect what side effect files
will be created, and for graphics files that are included
(so we can convert postscript to pdf if pdflatex is being run).
Now that this is recursive we could tighten up on the side
effect file list (e.g. a \makeindex with no \index commands
won't make all the files we tell scons to expect as side effects)
but I think that is asking for trouble if we mess it up.
|
