utils.pwsh: Fix Windows config paths#309
Open
RytoEX wants to merge 1 commit intoobsproject:masterfrom
Open
Conversation
Apparently, CMake can fail when parsing the current path string because it interprets the backslash as the start of an escape sequence. Modern Windows can interpret paths with forward slashes, so it should be safe to change these slashes.
d426148 to
b58d62d
Compare
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
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.
Description
Apparently, CMake can fail when parsing the current path string because it interprets the backslash as the start of an escape sequence. Modern Windows can interpret paths with forward slashes, so it should be safe to change these slashes.
Motivation and Context
Discovered this while attempting to update dependencies. Want to fix it separate from that update.
https://github.com/RytoEX/obs-deps/actions/runs/23963204885/job/69897580516#step:4:6211
How Has This Been Tested?
I haven't tested this change yet, but we use forward slashes in other paths for Windows elsewhere, so this is hopefully fine.
Types of changes
Checklist: