Add dependency on Config to check targets #523
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The targets used for config checks do not have a dependency on
/boost/config//boost_config. This is not a problem when the files are used as a part of the actual Boost.Config project. But consider this use case:/boost/configis generated for the user.-config.jamfile is generated for the user that points to the generated project viaIn this case Boost.Config's
build.jamis not used and so, the check targets cannot find the necessary headers.This use case is how Conan package manager works. So, the change is aimed to provide support for modular build to Boost libraries using Conan.