Boost logo

Boost :

Subject: Re: [boost] Interface for configuring third-party dependencies
From: Vladimir Prus (vladimir_at_[hidden])
Date: 2010-10-07 15:39:12

Rene Rivera wrote:

> On 10/7/2010 11:20 AM, Vladimir Prus wrote:
>> Second, it will possible to specify external dependencies in user-config.jam,
>> or any other configuration file. This approach is slightly more complicated,
>> as one has to edit a config file, but retains configuration and permits
>> to specify multiple configuration for an external dependency -- which
>> is not possible using environment variables. Roughly, the syntax will
>> be:
>> using zlib
>> : condition<target-os>windows
>> : include-path whatever
>> : library-path something-else
>> ;
>> The 'condition' parameter specifies when this declaration will be picked up.
>> Other parameters mirror the environment variables above.
> Since this is the replacement for the external library support extension
> I have..

Actually, as I've mentioned on IRC, it's not a replacement. Your extensions
allow to build external project -- this is mostly an interface how to specify
the location of pre-built things.

> I have one question.. Where would support for configuring the
> "variation" (i.e. what settings to use when the library/ies are used)
> fit in the above? Or is the above only for pre-built libraries?

I assume you mean usage requirements of library targets? At this level,
they don't exist -- this interface is meant to specify where to find
the library, and the actual implementation (e.g. zlib.jam) is responsible
to define appropriate targets (e.g. /zlib//zlib) so that their usage
requirements are right. In particular, in about all cases usage requirements
should contain <include>whatever property, as otherwise complication
again the library will fail.

Does this make sense?

- Volodya

Boost list run by bdawes at, gregod at, cpdaniel at, john at