Skip to content

Improve vswhere use to avoid boiling the ocean while looking for cl.exe #55

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

Merged
merged 2 commits into from
Dec 1, 2024

Conversation

touilleMan
Copy link
Collaborator

@touilleMan touilleMan commented Nov 30, 2024

close #48

@touilleMan touilleMan force-pushed the improve-vswhere-use branch 12 times, most recently from e924530 to f7d040e Compare November 30, 2024 09:28
@touilleMan touilleMan merged commit 65b3061 into master Dec 1, 2024
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

VSWhere search for cl.exe on Windows takes 500s on CI
1 participant