build_docs: mrdocs, clang compiler support #97
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
sdarwin
force-pushed
the
feature/build_docs11
branch
3 times, most recently
from
6486d0b to
791bb7b
Compare
sdarwin
force-pushed
the
feature/build_docs11
branch
from
791bb7b to
1434db7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Previous versions of build_docs did not install or require a C++ compiler.
Now it appears that MrDocs expects a local C++ compiler to be available.
Typically that will already be the case. However, rather than forcibly install clang on every system (especially Windows), the script will attempt to detect if MrDocs is used, and if Visual Studio is already available. In the critical case (mainly on Windows), prompt the user to go install Visual Studio before proceeding.