From: Markus Schöpflin (markus.schoepflin_at_[hidden])
Date: 2002-10-17 05:12:46
Vladimir Prus wrote:
> Markus Schöpflin wrote:
>> Vladimir Prus wrote:
>>> Markus Schöpflin wrote:
>>>> There is another use case I have: Linking to oracle libs. On
>>>> most platforms, you _have_ to specify very exactly what get's
>>>> linked and how. Currenty I'm using the fact that a rule name
>>>> can appear as the prerequisite of a target. For example:
>>>> exe hello : hello.cpp : link_to_oracle_libs ;
>>>> and link_to_oracle_libs is a rule which inserts the right
>>>> things in the linker command line depending on the current
>>>> build settings and platform. It would be great if something
>>>> like this would be supported in v2 as well.
>>> I think a minimal form of this is already supported. You can
>>> declare new target type ORACLE_EXE, and specify that it should
>>> be building in the same way as EXE, but with certain additional
>>> properties. Those properties can be computed dynamically.
>> This will do in my special use case. But a more general solution
>> to this would be nice.
> Do you have an idea of an approach that you'd like. I think that in
> general, if you want something special when linking certain kind
> of apps, you have to either use a different main target type, or
> some additional requirement. In either was, some custom code will
> be invoked to adjust build properties.
User defined features would be a nice thing, I think. Something like
exe foo : foo.cpp : <oracle-link>static ;
and <oracle-link> is a feature defined by me somewhere else.
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