Le 17 juin 2012 à 13:53, Stefano Lattarini a écrit :
> The use of '--build-dir' also allows us to specify different build
> directories for the PDF and DVI output, preventing the rules building
> them from stomping on each other's feet when run in parallel. This is
> demonstrated by the test case XXX, which before this change failed if
> run with MAKE="make -j2", but now succeeds even in that case.
You don't need that, the build-dir is structured so that you
don't have to. You can use a single build-dir for all the builds.
$ cat foo.tex
\documentclass{article}
\begin{document}
Hello, world!
\end{document}
$ texi2dvi -q --build-dir=build.t2d foo.tex --pdf -o foo.pdf
$ texi2dvi -q --build-dir=build.t2d foo.tex --dvi -o foo.dvi
$ texi2dvi -q --build-dir=build.t2d foo.tex --ps -o foo.ps
This is dvips(k) 5.991 Copyright 2011 Radical Eye Software (www.radicaleye.com)
' TeX output 2012.06.18:0936' -> foo.ps
</opt/local/share/texmf-texlive/dvips/base/tex.pro>
</opt/local/share/texmf-texlive/dvips/base/texps.pro>.
</opt/local/share/texmf-texlive-dist/fonts/type1/public/amsfonts/cm/cmr10.pfb>
[1]
$ ls build.t2d
foo.t2d
$ ls build.t2d/foo.t2d
dvi pdf tex_help
$ ls build.t2d/foo.t2d/pdf
bak build
$ ls build.t2d/foo.t2d/dvi
bak build
$ texi2dvi -q --build-dir=build.t2d foo.tex --pdf -o bar.pdf
$ ls build.t2d/
bar.t2d foo.t2d
