From: Vladimir Prus (ghost_at_[hidden])
Date: 2007-07-23 00:53:12
Daniel Wallin wrote:
> Roland Schwarz wrote:
>> I tried your suggested scriptlet, but there is a problem with the
>> make-name rule which is invoked from the <conditional>:
>> It does not have access to the name of the target. If I follow your
>> suggestion blindly I would have to supply an unique make-name for each
>> and every library. I guess this was not your suggestion.
>> Then I tried to use the <tag> rule like so:
>> lib boost_program_options : : <name>real_name <tag>@tag ;
>> This looks better, because it does give me access to all needed
>> information, but now I cannot change the name that is handed to the -l
>> switch for the linker. Just "return decorated_lib name ;" does nothing
>> Do you have any suggestions what I could try next?
> I'm not completely up to speed with this discussion, but how about
> deriving a new generator from `searched-lib`?
Or more specifically, introducing new type 'boost-lib' and creating
a generator for it. That's ultimately best solution.
As Roland notes, what I've posted is raw sketch -- it's possible
to make it support all boost libraries but it will require lots of
copy-paste, and generator (that has access to requested target name),
is in position to do this cleanly.
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