Re: [Boost-build] Using 'explicit' targets

Subject: Re: [Boost-build] Using 'explicit' targets
From: Edward Diener (eldiener_at_[hidden])
Date: 2016-05-16 10:48:03

On 5/16/2016 10:00 AM, Steven Watanabe wrote:
> AMDG
>
> On 05/16/2016 03:02 AM, Edward Diener wrote:
>>
>> This is not documented as far as I can see. In particular:
>>
>> target-id -> (project-id | target-name | file-name )
>>               | (project-id | directory-name) "//" target-name
>>
>> tells me that directory-name must be followed by "//" and a target name
>> to be valid. Instead you are now saying that directory-name alone is a
>> valid target-id.
>>
>
>   You're right.  The documentation is wrong
> here.  Any place that takes a project-id also
> accepts a directory.
>
> Example:
> alias system : ../boost-git/libs/system/build ;

Shouldn't that be that anyplace that takes a target-id also accepts a 
directory ?

Also I don't think that "project-id" is ever really defined anywhere.

>
> I've updated the documentation and also
> fixed a few other errors.
>
> - The order of checking is target-name, then
>   file-name, then project-id, then directory-name,
>   not project-id, then target-name as the documentation
>   implies.
>
> The implementation actually supports
> (project-id | directory-name) "//" target-id
> However, I've left this extra generality
> undocumented for now, as I've never seen
> any need for it outside of Boost.Build
> internals.

Thanks for updating the docs.