Bug 405872 - Certain library files installed to the wrong directory.
Summary: Certain library files installed to the wrong directory.
Status: RESOLVED NOT A BUG
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-25 22:19 UTC by halo117nachos
Modified: 2019-03-26 08:18 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description halo117nachos 2019-03-25 22:19:23 UTC
This is a build issue.

Here's my problem. I wanted a newer version of KDEConnect that what's available for my distro, so I'm trying to build KDEConnect from source. However, when I install it, several important library files get installed to /usr/lib/i386-linux-gnu. This is weird, since my system is 64 bit, thus the files should be installed to /usr/lib/x86_64-linux-gnu. AFAIK, nothing gets installed to /usr/lib/x86_64-linux-gnu. IDK if I'm doing something wrong, or if there's a bug in cmake, or what.

I got KDEConnect from this git repository: https://invent.kde.org/kde/kdeconnect-kde.git

These are the commands I ran:
mkdir build
cd build
cmake -DCMAKE_INSTALL_PREFIX=/usr ..
make
sudo make install

KDEConnect works, and I'm able to pair my laptop to my phone, but I can't do anything beyond that: I can't browse the device (via sftp), I can't read/send SMS messages... heck, I can't even see how much battery my phone has.

Creating a symlink in "/usr/lib/x86_64/qt5/plugins/kdeconnect", and having said link point to "/usr/lib/i386-linux-gnu/qt5/plugins/kdeconnect" seems to fix the issue (kdeconnectd will need to be restarted), but I find it odd that I even need to do that.

I'm running Ubuntu 18.04. I don't know much about make or cmake, so IDK what I can do on my end.
Comment 1 Erik Duisters 2019-03-26 08:18:31 UTC
You will have to find out how your systems packages are build and use the same cmake parameters so the files get installed into the right places.