Repository navigation
Conversation
|
@pdimov, @grafikrobot: is there anything I can do to help get this merged? |
|
We are going to need to make sure all the other PRs are reflected in the master branch. AFAICT |
|
Or maybe some of them? @mattst88 can you list what other changes this depends on? |
|
All the PRs are listed in the initial comment. boostorg/config#556 is the only one that's still outstanding. (Sorry, I'm unaware of how things flow into this repository) |
|
This PR depends on the Config one, so I don't think we should merge it yet. Also, it needs to be against |
|
The b2 changes haven´t made it to the bundled b2. And the prefer changes haven´t made it to master. I'm working on those. Looks like context changes are in master. |
Jamroot applies boostcpp.platform to the whole /boost project, and its deduce-architecture rule had no Alpha entry. find-builds then matched nothing, the rule returned early, and a build on Alpha got neither <architecture> nor <address-model> set for any library. alpha goes first in both .deducible-architectures and the find-builds argument list: the rule indexes the former with the result of the latter, so the two have to stay in the same order.
|
Thanks. Retargeted the PR to the |
|
Thanks @mattst88 . I'm getting close to getting the predef changes ironed out for master (tonight or tomorrow on this). But I'm waiting on one verification on a b2 fix to be able to reflect that into the boost tree. :-( |
Jamroot applies boostcpp.platform to the whole /boost project, and its deduce-architecture rule had no Alpha entry. find-builds then matched nothing, the rule returned early, and a build on Alpha got neither nor set for any library.
alpha goes first in both .deducible-architectures and the find-builds argument list: the rule indexes the former with the result of the latter, so the two have to stay in the same order.
See also