Re: [jamboost] [UI] system libraries

From: David Abrahams (dave_at_[hidden])
Date: 2002-12-02 09:10:00

Vladimir Prus <ghost_at_[hidden]> writes:

> David Abrahams wrote:
>
>>>
>>>Right. And what that "small description file" would contain? IMO,
>>>it can contain just a list of prebuilt targets. You then would use
>>>that file just like a regular project. For example, if that file
>>>lives in
>>>
>>> /space/pool ;
>>>
>>>you'd write
>>>
>>> use-project /pool : /space/pool ;
>>>
>>>and will access the target in 'pool' as it they were regular targets.
>>>But actually, they are pre-created and installed target. You need
>>>no access to sources.
>>>
>>>I fail to understand how it's different from Ullrich's idea. 
>> 
>> 
>> I don't see any place for a description of the build properties that
>> have been used to generate these prebuilts to appear. That was central
>> to what Ullrich was talking about.
>
> Properties used to build targets become requirements on prebuilt targets:
>
> prebuilt LIB helpers : helpers.a : <variant>release ;
> prebuilt LIB helpers : helprer_d.a : <variant>debug ;
>
> It's that enough?

I don't think so.
At least, it's not very clearly specified what you mean.

Does <variant>debug mean just that the debug variant was used, or that
the full set of build requirements used to build helprer_d.a was
derived from nothing more than just <variant>debug? Does it imply
<debug-symbols>on was used? Suppose that's in the requirements for
some dependent target?

-- 
David Abrahams
dave_at_[hidden] * http://www.boost-consulting.com
Boost support, enhancements, training, and commercial distribution