Respect PATHEXT when looking for Win executable #2298
Merged
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
... as idiomatic in Windows programming.
uranusjr
force-pushed
the
windows-find-executable-pathext
branch
from
cdb6b17
to
d48e97e
Compare
|
Buildkite failure was the non-deterministic build failure for the |
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.
On Windows, the environment variable
PATHEXTholds a list (;-separated) of extensions that Windows use to look up an executable file when the user enters a (extension-less) command into the prompt. This rewrite makesfind_windows_executablemimic this behaviour.Fix #2282.