Skip VS 2022 compatibility setup steps if the toolchain is newer than 5.9 #34
Conversation
This file contains 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
|
@compnerd I forget exactly why we don't need this when the toolchain is newer than 5.9. Can you remind me so I can capture that in the PR description? |
|
Because the compiler will inject the modulemap via the VFS overlay which avoids the need to explicitly copy the modulemap to the destination. |
Thanks! |
compnerd
approved these changes
May 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
After 5.9, the compiler will inject the modulemaps from /usr/share to the correct destination using via the VFS overlay which avoids the need to explicitly copy.