-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Find the correct install paths for systemd units and udev rules #2046
Find the correct install paths for systemd units and udev rules #2046
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm assuming these FindX files are not re-used from anywhere.
I tried searching, but the closest I found was
Looks like some linting errors to fix, and it fails on debian distros. Does something else need to be installed there? |
I was inspired by: And further the cmake docs |
Should work. I only tested the fedora 39 container locally. I will check debian based containers later and also replace tabs with spaces for the linter. My vscode went wild with all the different formatting in the cmake files ;). |
Linting should be fixed now and indeed Also the variable for querying the systemd unit install dirs did not work on Ubuntu 20.x. Now using an older alias that works on all distros. Tested all docker files locally so I think everything should work now :). |
The Ubuntu 20.x uses an older systemd version. Both variable names work for all distros.
a379c64
to
ee34af3
Compare
Description
Instead of using
CMAKE_INSTALL_LIBDIR
to get the system lib directory where a library would be installed (can be 'lib' or 'lib64'), now the actual install path ofsystemd
andudev
are queried viapkg-config
. This should be more reliable for linux builds.My knowledge of
cmake
is limited so a review would appreciated.Issues Fixed or Closed
Type of Change
.github/...
)Checklist
Branch Updates
LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.