Skip to content

Conversation

pdimov
Copy link
Member

@pdimov pdimov commented Jun 30, 2017

BOOST_STAGE_LOCATE is undefined in boost-install, so it always uses the target name, stage. This means that when b2 stage is invoked from, f.ex. libs/system/build, a local libs/system/build/stage directory is used for staging. This is almost certainly wrong. In addition, BOOST_STAGE_LOCATE in boostcpp is by default the relative path stage, so even if used with modules.peek, it works the same way.

I'm not entirely sure that the proposed replacement is correct in all use cases, but it's an improvement. :-)

@pdimov
Copy link
Member Author

pdimov commented Oct 14, 2017

Opinion on this @vprus? BOOST_STAGE_LOCATE is used undefined, this can't be correct?

@pdimov pdimov merged commit 71fb0e1 into develop Dec 17, 2017
@pdimov pdimov deleted the pdimov-patch-2 branch December 17, 2017 01:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant