New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to configure plugins and libexec installation destination #69
Comments
Your solution might almost work, I think the problem is that you are passing absolute paths while it expects relative paths to CMAKE_INSTALL_PREFIX there (that's why you get the weird paths in the error message). A few lines down from your patch it computes the relative paths between various components, so they find each other. So either you pass in relative paths to begin with, or you can probably handle the absolute path case there. While your alternate libexec dir should be no problem, I don't really like the plugin path ;-) |
Yay, relative LIBEXEC_INSTALL_DIR works :-) For the plugins, I was only trying to change /usr/lib64/gammaray to /usr/lib64/qt4/plugins/gammaray (the rest of the path is fine) but you are right about them not really being Qt plugins. I tried setting PLUGIN_INSTALL_DIR=plugins (just for fun ;-)), but then the path was expanded to $pwd/plugins/, so make install installed the plugins into the build directory, while their .desktop files ended in CMAKE_INSTALL_PREFIX/plugins, as expected. |
Can we close this? |
Passing
-DLIBEXEC_INSTALL_DIR=/usr/libexec/gammaray
to CMake has no impact and gammaray-launcher and gammaray-client are always installed to /usr/lib64/gammaray/libexec. Although this is a good default, it would still be nice if packagers could choose the destination (e.g. /usr/libexec/gammaray, as recommended by Fedora packaging guidelines).Passing
-DPLUGIN_INSTALL_DIR=/usr/lib64/qt4/plugins
to CMake is ignored by all plugins (they install to /usr/lib64/gammaray/version/qt-build/), except for gammaray_kjobtracker, which installs to /usr/lib64/plugins/version/qt-build/.I tried making the variables configurable by users (see the patch below), which worked for plugins, but has broken lookup of the libexec utilities:
libexec is usually not in PATH, so it does not work :)
The text was updated successfully, but these errors were encountered: