Clarify source build docs for qt6 branch and cmake compat #124
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.
Summary
qt6branch, including the correctgit clone -b qt6command-DCMAKE_POLICY_VERSION_MINIMUM=3.5workaround for cmake 4.0+ users encountering policy errors from older submodules (e.g. eglut)Addresses #120
Context
As reported in #120, the source build guide previously only showed how to clone the default (main/Qt5) branch, which is deprecated. The warning box mentioned the qt6 branch but didn't explain how to actually use it. Users building from source with cmake 4.0+ would also encounter cmake policy version conflicts from submodules like eglut that specify cmake 3.5, with no guidance on how to resolve them.
Test plan
#building-the-qt6-branch-recommended) resolves correctly in the rendered mdbook outputgit clone --recursive -b qt6correctly pulls the qt6 branch with submodules