Re: [jamboost] Re: Executing additional tools after build step

From: Andrey Melnikov (melnikov_at_[hidden])
Date: 2005-09-20 14:26:50

David Abrahams wrote:
> Vladimir Prus <ghost_at_[hidden]> writes:
> 
> 
>>I think it would be good to add a target that just runs some command, without 
>>creating any files. When such target is built, the command is just run, and 
>>no up-to-date checks are made for any files.
> 
> 
> Your phraseology is a little confusing, because bjam does all its
> up-to-date checks before deciding to build anything. But anyway, I'll
> ask:
> 
> Not even for files that the target may depend on? That seems like a
> needless and restrictive limitation. It seems like it would be more
> useful if the target were only built when its dependencies (if any)
> were outdated.
> 
For me the desired behaviour is the following. The files the target 
depends on should be built if they are outdated. The target itself will 
be built (executed) unconditionally, even if the dependencies are up to 
date.

This is good for commands that don't save their results. For example, a 
command can process some files and just produce a message.

A real life example for this is running CppUnit tests using a BJam/Nmake 
project under Visual Studio.

Andrey