Skip to content

Fix CMAKE_INSTALL_PREFIX init behavior on Win32.#1602

Merged
TorreZuk merged 1 commit into
ROCm:developfrom
marbre:cmake_win32
May 9, 2025
Merged

Fix CMAKE_INSTALL_PREFIX init behavior on Win32.#1602
TorreZuk merged 1 commit into
ROCm:developfrom
marbre:cmake_win32

Conversation

@marbre
Copy link
Copy Markdown
Member

@marbre marbre commented May 7, 2025

Per the guidance at https://cmake.org/cmake/help/latest/variable/CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT.html, CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT can be "used by project code to change the default without overriding a user-provided value".

This allows users and integration projects like https://github.com/ROCm/TheRock to set an install path of their choosing while still defaulting to this project's preferred value if the value is not already set. For more context, see ROCm/TheRock#343.

Copy link
Copy Markdown
Contributor

@TorreZuk TorreZuk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Windows test failures are unrelated. Looks fine.

@TorreZuk TorreZuk merged commit 054002e into ROCm:develop May 9, 2025
19 of 20 checks passed
@marbre marbre deleted the cmake_win32 branch May 13, 2025 08:38
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.

3 participants