Allow custom CMAKE_INSTALL_RPATH #768
Merged
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
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.
When building ClamAV libraries for integration, it is not unusual for the shared library files to be installed in a directory that is convenient in the build environment, but deploy them in a different directory.
E.g., The build environment may install to:
But it may be necessary to deploy to:
ClamAV's default behaviour is to set
RPATHto the absolute path of the build environment's "lib" directory. This make those files difficult to deploy without patching.It is more flexible if integrators have full control over RPATH. This change allows integrators to set CMAKE_INSTALL_RPATH and override the default behaviour.
Reference: CMake Wiki RPATH Handling