Re: [jamboost] Executing additional tools after build step

From: Bojan Resnik (resnikb_at_[hidden])
Date: 2005-09-19 04:54:48

> You can use the following:
> 
> exe main : main.cpp ;
> notfile main_postprocess : @postprocess : main ;
> actions postprocess
> {
> do_something $(>)
> }
> 
> (Provided you use the CVS version).
> 
> For convenience, I attach my email describing this feature.

Thanks, this indeed solves this problem.

I have been thinking of the problem a bit more, and I was wondering
if a more general solution might be possible. For example, developing
addins for third-party
products usually requires defining some symbols, specifying
third-party include and lib directories, additional libraries, and
sometimes even running special tools after the build is done. It would
be convenient if all that could be wrapped ina different target type,
so that, for example: 

foo-addin bar : [ glob *.cpp ] : <include>. ;
  
would have the same effect as something along the lines of:

exe bar : [ glob *.cpp ] /foo//lib : <include>. <include>/foo/include ;
notfile bar_post : @foo-post : bar ;
actions foo-post
{
/foo/bin/post $(>)
}

Now that I am writing about this, it seems to me that the python
extension support implements something like this. I will have a closer
look at that.

Regards,
Bojan Resnik