Support installing package configuration files at different location #468
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.
This change allows the user to define a location for the CMake and pkg-config configuration files while installing the libraries, e.g., at a "default" location.
This will hopefully help for the use case described in #425.
@opoplawski: Would that work for your use-case?
You could, e.g., configure with
That would allow to install the headers to a separate location like you already proposed in #425. Additionally, it would allow to install the CMake package configuration files and the .pc files in a location that differs from the "usual" one.
However, the libraries themselves would still be installed at the default location (with the SUFFIX that you were using). So, no RPATH or LD_PRELOAD shenanigans would be needed.
When building projects that rely on the "non-default" variants, users would need to set one of the following (depending on their choice of build system):
What do you think?