Do not install plugins in CMAKE_INSTALL_LIBDIR #1316
Closed
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.
BEGINRELEASENOTES
CMAKE_INSTALL_LIBDIR
, but always inlib
ENDRELEASENOTES
CMAKE_INSTALL_LIBDIR
can change between cmake versions for the same OS and since everything is hardcoded to uselib
it is unexpected that the plugins are installed somewhere else. In practice it happens thatCMAKE_INSTALL_LIBDIR
is set almost always (but not always, sometimes it is set tolib64
, see https://cmake.org/cmake/help/v3.30/module/GNUInstallDirs.html) tolib
. This is something that can be of course solved from the packaging point of view, but I think it would be a good practice to either set everything toCMAKE_INSTALL_LIBDIR
(which could change) or everything tolib
(this PR).Given that the inclusion of both non-plugins libraries and plugins libraries in
LD_LIBRARY_PATH
to make DD4hep work fine having everything in the same directory I think is a good idea. Otherwise another variable could be added if someone wanted to install the plugins in a different location.