Fix issue with ocio_depts handling spaces in file paths #2109
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
Signed-off-by: Taegyun Ha <[email protected]>
DevTGHa
force-pushed
the
windows-script-fix
branch
from
20a848f to
efbb8bb
Compare
cozdas
approved these changes
Jan 6, 2025
doug-walker
approved these changes
Jan 6, 2025
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.
share/dev/windows/ocio_deps.batwas not able to find the installed visual studio location due to the space in the paths. This is becausefor /fsplits on spaces and tabs by default.For example,
C:\Program Files (x86)becomesC:\Program.Adding
delims=to avoid splitting the output of the command and keeps the entire path in%%i.