Re: [jamboost] .OUT extension instead of .EXE (Was:multiple steps when linking with a new tool)

From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-11-12 02:40:51

On Friday 12 November 2004 02:40, Van Nguyen wrote:

> Now I'm having problems trying to generate .out file instead of .exe
> file. I kinda hacked it a little bit with builtin.jam where I added:
>
> [...]
> declare-type NT CYGWIN : OUT : out : : ;
> declare-type : OUT : : : ;
> [...]
> rule __init__ ( name : project : sources * : requirements * :
> default-build * : usage-requirements * )
> {
> if ccsimpc in [ modules.peek : ARGV ]
> {

This is already wrong, no code in tools/* should even peek at ARGV except for 
checking debugging options. This won't work when two toolsets are required. 

Besides, you seem to be hacking 'exe-target-class'. Those 'target-classes' are 
deprecated, and in fact, 'exe-target-class' will disappear from CVS very 
soon. If you need to customise anything you better use generators.

Finally, are you trying to change the extension of type EXE for your toolset? 
The docs at

http://www.boost.org/boost-build2/doc/html/bbv2/extending/targets.html

mention a 'type.set-generated-target-suffix' rule which should help you out. 
You can check the docs for that rule, and example usage in builtin.jam. In 
the meanwhile, I'll add an example to the docs.

> Also, since a new toolset is added, here's a list of files I think
> that need to be updated accordingly.
>
> build/build_request.jam
> build/feature.jam
> build/generators.jam
> build/property.jam

Why? Once a new toolset is added, a user can say

using <new-toolset> ;

in his user-config.jam. There's no need to change those files, unless you made 
some specific fixes there.

- Volodya