-
Notifications
You must be signed in to change notification settings - Fork 127
[native_toolchain_c] Fix #3327 native_toolchain_c vswhere selection #3328
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Chaos02
wants to merge
2
commits into
dart-lang:main
Choose a base branch
from
Chaos02:fix/native-toolchain-c-vswhere-requires-3327-clean
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is only for if the target is
Architecture.x64. ForArchitecture.arm64it should beMicrosoft.VisualStudio.Component.VC.Tools.ARM64. But,VisualStudioResolverdoesn't take a target architecture, we're trying to find one visual studio.So maybe a better fix is to first try
'Microsoft.VisualStudio.Component.VC.Tools.x86.x64', then add all instances withparseVswhereand then do the same withMicrosoft.VisualStudio.Component.VC.Tools.ARM64.We should probably try to run a CI on
runs-on: windows-11-armin.github/workflows/native.yamlto cover the CI. (But we can do that as a separate PR.)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, given that the actual choosing is done in the caller, we should return all of the possible instances and implement choosing logic for the architecture somewhere here perhaps?
https://github.com/Chaos02/native/blob/812bd1bd6376f0f898627a11ea4c935fe3a544c4/pkgs/native_toolchain_c/lib/src/native_toolchain/msvc.dart#L228-L257
or maybe even here?
https://github.com/Chaos02/native/blob/fix/native-toolchain-c-vswhere-requires-3327-clean/pkgs/native_toolchain_c/lib/src/native_toolchain/msvc.dart#L41-L127
I'll suggest something, let me know if it sounds good to you
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would you rename the x64 (old) resolver to VisualStudioX64 or leave it be and just suffix the newer ones?
https://github.com/Chaos02/native/blob/d4f3cb61eb8062802e48a2b9038868e4b243f363/pkgs/native_toolchain_c/lib/src/native_toolchain/msvc.dart#L317
like here:
https://github.com/Chaos02/native/blob/d4f3cb61eb8062802e48a2b9038868e4b243f363/pkgs/native_toolchain_c/lib/src/native_toolchain/msvc.dart#L304