CPACK_PACKAGING_INSTALL_PREFIX added to CMakeLists.txt - #11
Open
MikePooh wants to merge 1 commit into
Open
Conversation
Member
|
Doesn't it makes more sense to actually define a different CPACK_PACKAGING_INSTALL_PREFIX when you want to use cpack as the docs says each generator has it's own default.. |
Contributor
Author
|
I am not familiar with that. I've just met a problem - package made with cpack has install paths different from paths done with just 'make install'. In the first case it was /usr/* in second one it was /usr/local/*. It causes problems with plugin finding. Maybe there is better solution.. |
This file contains hidden or 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
2 participants
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.
Before this commit CPack installs the files to default /usr/* directory and this caused problem with plugins searching