From: David Abrahams (dave_at_[hidden])
Date: 2004-10-23 00:25:22
David Abrahams <dave_at_[hidden]> writes:
> Vladimir Prus <ghost_at_[hidden]> writes:
>> David Abrahams wrote:
>>> > Maybe I'm starting to get your idea, though I need to digest it
>>> > more. I'm not yet sure why current Jamfiles are not portable or
>>> > interoperable.
>>> Suppose two projects choose the same project ID but need to be used
>>> together by some other project?
>> This is probably not as big problem as it seems. After all, all system-wide
>> libraries have to have different names already and it does not cause big
>> problems. But yea, a clash is possible.
> Don't forget, some project may need to know about two different
> versions of boost :-)
>>> > , or that /boost specified in 'use-project' overrides whatever was
>>> > specified there?
>>> That would be OK too. It begins to sound like "project IDs that have
>>> only local effect" that I described above.
>> Yea, kind of. For example, I can have two copies of boost and happily use them
>> use-project /boost-stable : some-path ;
>> use-project /boost-unstable : some-other-path ;
Is there any chance of getting the features discussed in this thread
into an upcoming milestone? This is the only functionality that
really makes sense to me, so it becomes a de-facto prerequisite for
me before I can really document how target references work ;-)
-- Dave Abrahams Boost Consulting http://www.boost-consulting.com
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