Skip to content

Fix ocio.bat: create build/install directories if missing - #2346

Open
hikmetba-bit wants to merge 1 commit into
AcademySoftwareFoundation:mainfrom
hikmetba-bit:fix/ocio-bat-create-build-install-dirs
Open

hikmetba-bit wants to merge 1 commit into
AcademySoftwareFoundation:mainfrom
hikmetba-bit:fix/ocio-bat-create-build-install-dirs

Conversation

@hikmetba-bit

Copy link
Copy Markdown

Summary

Fixes #2031.

Without --configure, cmake -B never runs, so BUILD_PATH and INSTALL_PATH are never created on disk. The subsequent cmake --build, cmake --install, and ctest steps then fail with an error like C:/TEMP/OCIO/build/Release is not a directory, as reported in the issue.

Fix

Explicitly create both directories with mkdir right after they are resolved, regardless of whether --configure was passed on that run.

Test plan

  • Ran ocio.bat --help before and after the change to confirm the script still parses correctly.
  • Verified in isolation (cmd /c "if NOT EXIST ... mkdir ...") that the two added lines create nested build/install directories that don't yet exist, and are a no-op when they already exist.

🤖 Generated with Claude Code

Without --configure, cmake -B never runs, so BUILD_PATH and
INSTALL_PATH are never created. The subsequent cmake --build,
cmake --install, and ctest steps then fail with errors like
"C:/TEMP/OCIO/build/Release is not a directory".

Explicitly create both directories after they are resolved,
regardless of whether --configure was passed.

Fixes AcademySoftwareFoundation#2031

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@linux-foundation-easycla

Copy link
Copy Markdown

CLA Not Signed

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.

Should ocio.bat create the required build and install location directories?

1 participant