Re: [jamboost] Re: Hitting some walls when extending v2

From: Zbynek Winkler (zw-bjam_at_[hidden])
Date: 2005-09-28 14:08:26

Alexey Pakhunov wrote:

>>IMO too. But what else can I do when I am given these options:
>> 
>>
>Can't you call it as 'pdflatex foo/bar/somefile.ext'?
> 
>
Sure I can. It then compiles the foo/bar/somefile.ext into somefile.pdf 
but this somefile.pdf will be in the current directory along with 
somefile.aux, somefile.log a possibly others :(

>>In addition to that it generates a lot of junk files in the current 
>>directory and expects to find them the next time it is run :(((
>> 
>>
>This is not a problem actually. 
>
It is because these files are generated to the current directory.

>Let's say the first call will create 
>foo.txt and bar.txt in bin/debug. 
>
If only it did that :(

>The second time the tool will be 
>called in the same 'bin/debug' directory if the set of features remains 
>the same. So it will find foo.txt and bar.txt.
> 
>
I have not found a way to generate all the files in other than current 
directory. That is why I want to do

cd target/dir
pdflatex ../../somefile.tex
cd ../..
exit %status%

in the action. Actually after a sucessfull run I want to grep 
somefile.log for notifications about unresolved references. In that case 
I need to run the tool again (I believe up to 3 times).

Zbynek