Re: [Boost-build] Changed (wrong?) behavior with make/common.copy in master

Subject: Re: [Boost-build] Changed (wrong?) behavior with make/common.copy in master
From: Chambers, Matthew (matt.chambers42_at_[hidden])
Date: 2018-07-06 22:22:29

On 6/8/2018 11:36 PM, Steven Watanabe via Boost-build wrote:
> On 06/08/2018 01:12 PM, Chambers, Matthew via Boost-build wrote:
>> On master (c3dc95d3ac0219a0f774e6d382ed91d290cbde80) the behavior of my
>> old make/copy targets has broken. With this simple Jamroot:
>>> make copied.txt : others/others.txt : common.copy ;
>>> make copied.txt : darwin/darwin.txt : common.copy : <toolset>darwin ;
>>>
>>> actions make_libsettings
>>> {
>>>  Â Â Â  echo boo > "$(<[1])"
>>> }
>>> make bar.txt : : @make_libsettings : <location>bin/foo
>>> <dependency>copied.txt ;
> This change is intentional.  Boost.Build no longer
> includes path components that do not affect the
> build settings.  You can use <relevant>toolset
> to force Boost.Build to include the toolset in
> the path.  It will also work if you make copied.txt
> depend on any compilation target.
>
Thanks for the quick answer Steven. There's aspect of the old behavior I haven't been able to reproduce:

If I make a target depend on copied.txt from a different project (directory), how do I get the copied.txt's <location> to be based on the 
dependent target rather than the path components of the project that copied.txt is defined in?

Thanks,
-Matt