[prev in list] [next in list] [prev in thread] [next in thread] 

List:       boost-build
Subject:    Re: [Boost-build] prototyping alternative Boost.Build syntax
From:       Steven Watanabe <watanabesj () gmail ! com>
Date:       2016-11-07 17:02:15
Message-ID: 5820B397.1050209 () providere-consulting ! com
[Download RAW message or body]

AMDG

On 11/07/2016 09:45 AM, Stefan Seefeld wrote:
> 
>> - Most variables shouldn't be accessed from
>>   other modules anyway.
> 
> Here I'm not sure. I was wondering about large projects with multiple
> Jamfiles, where sub-project Jamfiles would inherit variables from
> 'outer' scopes (but could modify them locally). How does Boost.Build now
> handle this ? Is it using target-specific variables in most cases ?
> 

  Only variables defined by 'constant' and 'path-constant'
are inherited.  This is implemented by giving child
projects a copy of all inherited constants before
loading the Jamfile.

In Christ,
Steven Watanabe

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
[prev in list] [next in list] [prev in thread] [next in thread]