Fix PATH variable handling on Windows #599
Merged
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.
Description
boost::process::environment
uses a case-sensitive match when looking up environment variables, but Windows variables (especiallyPATH
) tend to behave case-insensitively. Because the name of the Windows variable isPath
, notPATH
, we would attempt to concatenate;C:\Program Files (x86)\Steam
to thePATH
but end up overwriting the entire thing becauseenv["PATH"]
returned an empty string.Our
PATH
value itself was also incorrectly hardcoded such that a system where theProgram Files (x86)
folder (or the whole Windows installation) did not reside on the C: drive would not be able to launch Steam.Screenshot
Issues Fixed or Closed
Type of Change
.github/...
)Checklist
Branch Updates
LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.