[bind][function][lamda][signals][variant][boostbook] PDF doc builds broken?
The libs bind, lambda, signals, variant and boostbook all have: project boost/doc ; In their Jamfiles, and Boost.Build is now treating that duplication as an error. Is there any reason these project ID's can't be just commented out / removed? Thanks, John.
On 25 May 2013 12:39, John Maddock
The libs bind, lambda, signals, variant and boostbook all have:
project boost/doc ;
In their Jamfiles, and Boost.Build is now treating that duplication as an error.
Is there any reason these project ID's can't be just commented out / removed?
Not that I know of. Does 'project' have any function other than to specify requirements and other attributes?
AMDG On 05/25/2013 06:04 AM, Daniel James wrote:
On 25 May 2013 12:39, John Maddock
wrote: The libs bind, lambda, signals, variant and boostbook all have:
project boost/doc ;
In their Jamfiles, and Boost.Build is now treating that duplication as an error.
Is there any reason these project ID's can't be just commented out / removed?
Not that I know of. Does 'project' have any function other than to specify requirements and other attributes?
The project ID can be used to reference the project. e.g. /boost//headers works because Jamroot has project boost : ... ; In Christ, Steven Watanabe
AMDG On 05/25/2013 04:39 AM, John Maddock wrote:
The libs bind, lambda, signals, variant and boostbook all have:
project boost/doc ;
In their Jamfiles, and Boost.Build is now treating that duplication as an error.
Is there any reason these project ID's can't be just commented out / removed?
It's okay to remove the ID's. Project ID's have always been required to be unique. I'm not sure why it worked before. In Christ, Steven Watanabe
participants (3)
-
Daniel James
-
John Maddock
-
Steven Watanabe