| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
specific support for batched compilation for Microsoft Visual C/C++.
Merged revisions 3819-3851,3854-3869,3871-3877,3880 via svnmerge from
http://scons.tigris.org/svn/scons/branches/sgk_batch
........
r3820 | stevenknight | 2008-12-09 23:59:14 -0800 (Tue, 09 Dec 2008) | 6 lines
Issue 1086: Batch compilation support:
* $MSVC_BATCH to control Visual C/C++ batch compilation.
* New $CHANGED_SOURCES, $CHANGED_TARGETS, $UNCHANGED_SOURCES and
$UNCHANGED_TARGETS construction variables.
* New Action(batch_key=, targets=) keyword arguments.
........
r3880 | stevenknight | 2009-01-07 20:50:41 -0800 (Wed, 07 Jan 2009) | 3 lines
Use UniqueList objects to collect the all_children(), all_prerequisites()
and all_sources() lists instead of calling uniquer_hashables() by hand.
........
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
directory name. (Arve Knudsen)
|
| |
|
|
| |
link.
|
| | |
|
| |
|
|
| |
Knudsen.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Test that we don't make a .pdf file from the graphic.
The patch also covers the case of requiring the graphics files
I search for to have an extension so we don't try to build fig.eps from fig.eps...
|
| | |
|
| |
|
|
|
|
| |
failed when the .tex file is in a subdirectory.
I added a new test and made the one line fix.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This is already an action in gs.py
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Test of generating several .pdfs from a list of .ps (new single_source setting)
test/TEX/LATEX2.py
Based on second half of LATEX. generate all .pdf's at once by giving a list of .tex files
test of single_source
src/engine/SCons/Scanner/LaTeX.py
Add test of changing an included file.
Add test of included file having no extension
src/engine/SCons/Scanner/LaTeX.py
Add lists of acceptable graphics extensions,
In the furture make this user configurable??
Scan for files in the paths stored in env['TEXINPUTS'] and env['ENV']['TEXINPUTS']
for people who may just input their environment...
Add function findENVPatDirs for this purpose
src/engine/SCons/Tool/pdf.py
add epstopdf action
Have to add it after the pdftex action so it is not the default.
Make builder single_source since each input produces one output
src/engine/SCons/Tool/pdftex.py
use tex_eps_emitter
call pdf.generate2 to add epstopdf action after the PDFLaTeXAction
src/engine/SCons/Tool/dvipdf.py
simplify coding that adds the source directory to the search path TEXPICTS
src/engine/SCons/Tool/dvips.py
Add single_source option since each ps file comes from one dvi file
src/engine/SCons/Tool/pdflatex.py
add .tex as a valid extension and switch emitters to tex_pdf_emitter
src/engine/SCons/Tool/tex.py
fix regular expressions ^[^%]* to ^[^%\n]* for multiline environment
add REs for \input or \include and \includegraphics
get graphics extensions from Scanner.LaTeX so they are defined in one place
move modify_env_var to Scanner.LaTeX since it is used there and easier to import it here
add FindFile routine to find a file given name, list of suffixes, paths, env
returns a node for the file.
add tex_eps_emitter and tex_pdf_emitter that call a core routine with
a different list of graphics extensions that can be handled by the
tool used (latex vs. pdflatex)
revamp feature test/suffix list into two lists and build the list used
to create sideeffects for each input file...
These tests now get applied to each included file so the whole source
tree is tested.
Get list of paths from env['ENV']['TEXINPUTS'] and env['TEXINPUTS']
if find we need a .pdf file and only have .eps or .ps set up the
.pdf as a target with the .eps as source...
change emitter to tex_eps_emitter
src/engine/SCons/Tool/latex.py
add .tex as a valid extension and switch emitters to tex_eps_emitter
|
| |
|
|
| |
in place of popen2, and calling hashlib.md5() instead of the md5 module.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
sets it in tee dvi2ps and dvipdf tools where it is needed. This means that we
can reset it to the original value at the end of the tool.
This is done by storing the .tex source file's path in the
.dvi file's Node .attribute slot and retrieving it in the dvi2ps and dvipdf
tools from the source.
I also updated the list of graphics extensions in the Latex scanner
I set up one function that gets called to run either dvi2ps or dvipdf
after setting TEXPICTS.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Basic unittest included
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
doesn't search for substrings).
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
| |
all the right tools installed.
|
| | |
|
| |
|
|
| |
SDK versions. (Dmitri Rubinstein)
|
| | |
|
| |
|
|
|
| |
file to what the user requested in the target. Tex produces a standard name
based on the source so this was not being done.
|
| | |
|