Skip to content
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

Use CMAKE_INSTALL_FULL_* for absolute paths #23

Merged
merged 1 commit into from
Mar 11, 2022

Conversation

danielfullmer
Copy link
Contributor

Instead of using a combination of CMAKE_INSTALL_PREFIX and
CMAKE_INSTALL_, we should use CMAKE_INSTALL_FULL_.

If the CMAKE_INSTALL_ is an absolute path (e.g. in NixOS), then
prefixing it with another absolute path would be incorrect.
CMAKE_INSTALL_FULL_ already handles the case if
CMAKE_INSTALL_ is an absolute path. See:
https://cmake.org/cmake/help/latest/module/GNUInstallDirs.html

Signed-off-by: Daniel Fullmer [email protected]

Instead of using a combination of CMAKE_INSTALL_PREFIX and
CMAKE_INSTALL_<dirname>, we should use CMAKE_INSTALL_FULL_<dirname>.

If the CMAKE_INSTALL_<dirname> is an absolute path (e.g. in NixOS), then
prefixing it with another absolute path would be incorrect.
CMAKE_INSTALL_FULL_<dirname> already handles the case if
CMAKE_INSTALL_<dirname> is an absolute path. See:
https://cmake.org/cmake/help/latest/module/GNUInstallDirs.html

Signed-off-by: Daniel Fullmer <[email protected]>
@madisongh
Copy link
Member

Thanks again!

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