From: Pedro Ferreira (pedro.ferreira_at_[hidden])
Date: 2004-12-16 12:06:48
>> The basic idea is very good but, looking at the code, it seems this
>> will be called just once per target and modify all files generated by
>> that target the same way. To support the Windows case, I would need it
>> to be called once per generated file... Can you move the <tag> logic
>> down to the generator.generated-targets? Or are there any side-effects
>> I overlooked?
> Yea, we must be carefull to avoid applying <tag> to all targets. Say:
> lib a : a.cpp ;
> you don't want to apply <tag> to a.obj, right? Of course, this is doable,
> not as straight-forward as I'd like.
> BTW, I forgot to ask the most important question: why do you prefer to
> <tag> on targets, not on stage? To avoid relinking, or you have some other
> reasons. I suspect I'll need to write a FAQ entry on this.
Still Thursday and I already am too tired to recall this correctly :-)
The only thing I can remember is:
lib foo : foo.cpp ;
exe bar : bar.cpp foo ;
stage dist : exe : <tag>1.32.0
The staged exe will depend on libfoo.so and not on libfoo.so.1.32.0.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk