-
Notifications
You must be signed in to change notification settings - Fork 6
CI: Avoid recompiling hipFile in later stages of CI. #148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
46dbb75
ae07efe
caaf1b9
9c89853
de49102
dadaa9c
7a18ca0
2d4dd72
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -117,6 +117,17 @@ list(APPEND CMAKE_PREFIX_PATH | |
| /opt/rocm/hip | ||
| ) | ||
|
|
||
| # Set hipFile Install Path to the ROCm directory | ||
| # Note: CMAKE_INSTALL_PREFIX is set to a default by project(). | ||
| if(CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT) | ||
| set(CMAKE_INSTALL_PREFIX "${ROCM_PATH}" CACHE PATH "The path where hipFile should be installed" FORCE) | ||
| endif() | ||
|
|
||
| # Fix library install directory to "lib" to be inline with the rest of ROCm | ||
| # Note: If testing is enabled, installing GTest calls GNUInstallDirs which will | ||
| # set this before ROCMInstallTargets can set it. | ||
| set(CMAKE_INSTALL_LIBDIR "lib" CACHE STRING "Directory name for installed ROCm libraries") | ||
|
|
||
|
Comment on lines
+120
to
+130
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Would it be worth setting CMAKE_INSTALL_PREFIX on the configuration instead of changing the default? Also, when I test this, the
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. In TheRock,
I agree but point back to the limitation that currently exists in our CI. |
||
| #----------------------------------------------------------------------------- | ||
| # Import useful things for later | ||
| #----------------------------------------------------------------------------- | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know that it would be an archive inside of an archive, but would it be worth creating a tar archive for the build directory, so you don't have this list to maintain?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this list changes frequently then yes I think that would be worthwhile until we can figure out how to produce a "test" package compatible with CTest. Not too worried about it at this time though.