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

From: Zbynek Winkler (zw-bjam_at_[hidden])
Date: 2005-09-27 17:02:20

Alexey Pakhunov wrote:

>Zbynek Winkler wrote:
> 
>
>>1) Why does bb2 expect the target to be in directory "bin/debug"? How 
>>can I control this? I know I can change the 'bin' part by using 'project 
>>: build-dir something ;' -- how do I 'remove' the 'debug' part?
>> 
>>
>Short answer - you cannot control it. The directory name is constructed 
>from the actual feature set is used. By default ('bjam --v2') debug 
>variant is built. That is why you get bin/debug. But a user may pass 
>more features and the build directory will become /bin/debug/foo/bar.
> 
>
But why would anyone want their pdf files in bin/debug/foo/bar when 
those properties have no relevance to the pdf? I remember some time ago 
there was a discussion about marking some features (i)relevant. How did 
it end up?

>>3) I'd like to unconditionaly change to the output directory before 
>>executing pdflatex and then back again. 
>> 
>>
>IMO it is a bad idea.
>
IMO too. But what else can I do when I am given these options:

-efmt=FMTNAME use FMTNAME instead of program name or a %& line
-file-line-error-style print file:line:error style messages
-ini be pdfeinitex, for dumping formats; this is 
implicitly
true if the program name is `pdfeinitex'
-interaction=STRING set interaction mode (STRING=batchmode/nonstopmode/
scrollmode/errorstopmode)
-ipc send DVI output to a socket as well as the usual
output file
-ipc-start as -ipc, and also start the server at the other end
-jobname=STRING set the job name to STRING
-kpathsea-debug=NUMBER set path searching debugging flags according to
the bits of NUMBER
[-no]-mktex=FMT disable/enable mktexFMT generation (FMT=tex/tfm)
-output-comment=STRING use STRING for PDF file comment instead of date
-parse-first-line parse of the first line of the input file
-progname=STRING set program (and fmt) name to STRING
-recorder enable filename recorder
-shell-escape enable \write18{SHELL COMMAND}
-src-specials insert source specials into the DVI file
-src-specials=WHERE insert source specials in certain places of
the DVI file. WHERE is a comma-separated value
list: cr display hbox math par parend vbox
-translate-file=TCXNAME use the TCX file TCXNAME
-help display this help and exit
-version output version information and exit

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 :(((

>BB expects that the current directory will not be 
>changed and all filenames used by invoked tools will include path:
>
>actions
>{
> tool foo/bar/somefile.ext
>}
>
>But not
>
>actions
>{
> cd foo/bar
> tool somefile.ext
> cd ../..
>}
> 
>
As I see it I can either do this or create some wrapper program that 
will do it for me. But if you think this is not possible with BB then 
either the wrapper (I am not very keen of this option) or can start 
reading the scons documentations ;-)

>>3) When using the example scanner from documentation I am missing the 
>>proper extensions since they are not in the scanned file. When using the 
>>\includegraphics{something} pdftex searches for file something.ext where 
>>ext is taken form a list of extensions. The first one that matches is 
>>used. How would I do this in bb2?
>> 
>>
>You can try to generate all possible names from single file name and 
>establish dependencies on all of them.
> 
>
What happens when a target depends on a nonexistent file? That does not 
sound very healthy...

But thanks anyway.

Zbynek