CMake: adopt CMAKE_INSTALL_<dir> for install locations #93
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.
Suggestion cannot be applied right now. Please check back later.
When playing around with a multilib environment, I noticed that if our libs are built 64bit, those libs end up in (/usr/lib) aka /usr/lib32. This is caused because we hardcode all the install locations. Let us leverage the use of GNUInstallDirs to dynamically install binaries to the default install locations set by build systems and package generators.
This PR is part of a series of PR's
rdkcentral/Thunder#1604
rdkcentral/ThunderInterfaces#347
rdkcentral/ThunderClientLibraries#257
rdkcentral/ThunderNanoServices#789
rdkcentral/ThunderUI#99
WebPlatformForEmbedded/ThunderNanoServicesRDK#301
WebPlatformForEmbedded/ThunderLibraries#39