Adjust documentation relative paths #233
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 current Jamfile is counting on the git layout instead of the boost release layout to generate the documentation. We can check the links are now correct for the release layout with
b2 libs/process/docfrom the boost root directory. This PR adjusts the documentation Jamfile with apath-constantfor the doxygen command.This is circumstantially not very problematic at many places in the documentation because the b2 glob command interprets paths relative to the Jamfile (see boostorg/utility#86 (comment)), but that's not the case for all commands in there. For instance, the links on the headers like "Header <boost/process/child.hpp>" in the current reference page are broken. This PR should probably fix this problem.