Re: [Boost-build] Identifying target-name in jamfile

Subject: Re: [Boost-build] Identifying target-name in jamfile
From: Vladimir Prus (vladimir.prus_at_[hidden])
Date: 2016-05-30 06:38:13

On 30/05/2016 04:36, Edward Diener wrote:
> On 5/29/2016 4:59 PM, Steven Watanabe wrote:
>> AMDG
>>
>> On 05/29/2016 02:37 PM, Edward Diener wrote:
>>> On 5/29/2016 3:18 PM, Steven Watanabe wrote:
>>>>
>>>>   The rules like exe, run, obj, etc, register
>>>> the targets.  Each project essentially stores
>>>> a map of target names to main-target's.
>>>
>>> What does "registering a target" entail ? I have a non-local rule in a
>>> jamfile that evidently Boost Build recognizes as creating a target, but
>>> I don't know how Boost Build recognizes it as a target. Whatever
>>> "registering a target" means I am not doing this for the rule.
>>>
>>
>>   From the point of view of Boost.Build internals,
>> a project is effectively a container for targets.
>> When you call the rules for creating targets,
>
> Which are what ? All non-local rules in a jamfile are considered targets by Boost Build ?

Which are rules that ultimately call target.main-target-alternative. There's no special class
of rules, say, the 'exe' is just a function that ends up calling target.main-target-alternative
with the name passed as first parameter to it, and with a target object. If you create
a rule that does not do that, it will be just a function, no targets will be implicitly created.

-- 
Vladimir Prus
http://vladimirprus.com