Re: [Boost-build] Patch to fix dependency properties in project requirements

From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2008-07-19 17:21:09

AMDG

Jurko Gospodnetić wrote:
>   Hi Steven.
>
>>> #---------
>>> project abla : id kuku ;
>>> obj ooo : xxx.cpp ;
>>> explicit ooo ;
>>> exe xxx : kuku//ooo ;
>>> #---------
>
>   I just tested this and here are the results:
>
>   exe xxx : ooo ;         # works fine.
>   exe xxx : abla/ooo ;    # does not work.
>   exe xxx : /abla/ooo ;   # works fine.
>   exe xxx : kuku//ooo ;   # does not work.

These are expected

>   exe xxx : /kuku//ooo ;  # does not work.

I believe that this is a bug.  It's a result of the same
problem that caused the serialization tests to fail.

>   And changing the project id to /kuku makes no difference.
>
>
>   Unfortunately I'm not really home with the ideas behind these 
> project ids so I do not know what is the wanted behaviour. :-( Here 
> are some thoughts/questions below.
>
>
>   Is this the expected behaviour?
>
>   Do we want to change this behaviour?

Requiring project ids to start with / seems to be intended.
I'm just getting familiar with the code.

>   Should this be changed so all these combinations are accepted?
>
>   Should we expect project ids to be specified hierarchically starting 
> from / like folders do? Or should we expect all project ids to live in 
> a single global namespace?

Project ids are allowed to contain forward slashes.  For instance 
/boost/serialization/test
is a valid project id.

>   Are some sort of 'relative folder ids' allowed? What is the . or .. 
> equivalent then?
>
>   If some sort of 'relative folder ids' are allowed then how should 
> they be expanded in features (like those dependency features your 
> patch touches) to make them reference the same targets when applied in 
> different folders.

Projects can also be identified by the directory containing the 
Jamfile.  Oops,
that won't work correctly with my patch either.

project : requirements <library>relative/path/to/another/project//a ;

The path needs to be made absolute in translate-dependencies.
I'll add this to the test case, too.

In Christ,
Steven Watanabe