On Wed, Sep 2, 2020 at 2:43 PM <blfs-dev-requ...@lists.linuxfromscratch.org> wrote:
> Send blfs-dev mailing list submissions to > blfs-dev@lists.linuxfromscratch.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.linuxfromscratch.org/listinfo/blfs-dev > or, via email, send a message with subject or body 'help' to > blfs-dev-requ...@lists.linuxfromscratch.org > > You can reach the person managing the list at > blfs-dev-ow...@lists.linuxfromscratch.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of blfs-dev digest..." > Today's Topics: > > 1. Re: Fwd: Plasma-wayland-protocols install path (Pierre Labastie) > 2. Re: Fwd: Plasma-wayland-protocols install path (Marty Jack) > > > > ---------- Forwarded message ---------- > From: Pierre Labastie <pierre.labas...@neuf.fr> > To: blfs-dev@lists.linuxfromscratch.org > Cc: > Bcc: > Date: Tue, 01 Sep 2020 22:13:13 +0200 > Subject: Re: [blfs-dev] Fwd: Plasma-wayland-protocols install path > On Mon, 2020-08-31 at 16:40 -0500, Timothy Russo via blfs-dev wrote: > > I've been struggling to get kf5 plasma-framework-5.73.0 to compile > > and in my troubleshooting I came across the fact that plasma-wayland- > > protocols is hard coded to use /usr as the install prefix, but the > > installed directories shows it as $KF5_PREFIX/share/plasma-wayland- > > protocols. > > > > the cmake line needs to be cmake -DCMAKE_INSTALL_PREFIX=$KF5_PREFIX > > .. > > Hmmm, I haven't seen this. I've built plasma-wayland-protocols (in > /usr) before the frameworks, and everything went Ok. > > > > This didn't fix the problem I'm having with plasma-framework-5.73.0 > > though, which turned out to be some libraries in /usr/lib64 instead > > of /usr/lib. > > You may be lacking some sed in cmake and in extra-cmake-modules > > > I'm not sure how many of us are using KDE on LFS, but everytime I've > > tried to use build KDE I've run into tons of issues. xfce and even > > mate work great, Gnome is a little painful, but KDE is a huge pain to > > get working, and then it never seems quite right. > > The version ins 10.à worked without a problem for me. > > > Has anyone got KDEconnect to work with LFS? > > Thanks for mentioning this application, will give it a try. > > I see that the phone and the computer need to be on the same network, > so it does not work in a VM, unless using a bridge (which I don't use > ATM). > > Pierre > > > > > > ---------- Forwarded message ---------- > From: Marty Jack <marty...@comcast.net> > To: BLFS Development List <blfs-dev@lists.linuxfromscratch.org> > Cc: > Bcc: > Date: Tue, 01 Sep 2020 20:30:15 -0500 > Subject: Re: [blfs-dev] Fwd: Plasma-wayland-protocols install path > > > On Tue, 01 Sep 2020 15:13:13 -0500 Pierre Labastie via blfs-dev wrote: > > On Mon, 2020-08-31 at 16:40 -0500, Timothy Russo via blfs-dev wrote: > > > I've been struggling to get kf5 plasma-framework-5.73.0 to compile > > > and in my troubleshooting I came across the fact that plasma-wayland- > > > protocols is hard coded to use /usr as the install prefix, but the > > > installed directories shows it as $KF5_PREFIX/share/plasma-wayland- > > > protocols. > > > > > > the cmake line needs to be cmake -DCMAKE_INSTALL_PREFIX=$KF5_PREFIX > > > .. > > > > Hmmm, I haven't seen this. I've built plasma-wayland-protocols (in > > /usr) before the frameworks, and everything went Ok. > > > > > > This didn't fix the problem I'm having with plasma-framework-5.73.0 > > > though, which turned out to be some libraries in /usr/lib64 instead > > > of /usr/lib. > > > > You may be lacking some sed in cmake and in extra-cmake-modules > > > > > I'm not sure how many of us are using KDE on LFS, but everytime I've > > > tried to use build KDE I've run into tons of issues. xfce and even > > > mate work great, Gnome is a little painful, but KDE is a huge pain to > > > get working, and then it never seems quite right. > > > > The version ins 10.à worked without a problem for me. > > > > > Has anyone got KDEconnect to work with LFS? > > > > Thanks for mentioning this application, will give it a try. > > > > I see that the phone and the computer need to be on the same network, > > so it does not work in a VM, unless using a bridge (which I don't use > > ATM). > > > > Pierre > > > > -- > > http://lists.linuxfromscratch.org/listinfo/blfs-dev > > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > > Unsubscribe: See the above information page > > This works nicely for getting the lib64 eradicated. > > diff -Naur cmake-3.17.0.orig/Modules/GNUInstallDirs.cmake > cmake-3.17.0/Modules/GNUInstallDirs.cmake > --- cmake-3.17.0.orig/Modules/GNUInstallDirs.cmake 2020-03-20 > 06:26:14.000000000 -0400 > +++ cmake-3.17.0/Modules/GNUInstallDirs.cmake 2020-03-20 > 10:48:47.593776678 -0400 > @@ -241,9 +241,9 @@ > endif() > else() # not debian, rely on CMAKE_SIZEOF_VOID_P: > if("${CMAKE_SIZEOF_VOID_P}" EQUAL "8") > - set(_LIBDIR_DEFAULT "lib64") > + set(_LIBDIR_DEFAULT "lib") > if(DEFINED _GNUInstallDirs_LAST_CMAKE_INSTALL_PREFIX) > - set(__LAST_LIBDIR_DEFAULT "lib64") > + set(__LAST_LIBDIR_DEFAULT "lib") > endif() > endif() > endif() > If you wanted to install to /usr, the install path works fine, but if you were planning on using /opt I don't think it works as well. I tried both ways, and seemed to have better luck using /opt Thanks for the tips for the lib64 folder... it wasn't any of the kde stuff going to lib64 though, it was openGL that got put there. I was able to KDE fully working. The KDE connect app sort of worked for a bit, I could receive text messages to the app, but couldn't reply to them. I loaded a few more packages like akonadi, kmail, kontact, etc and got my contact names to show up instead of phone numbers, but still couldn't reply to messages. Then it just started crashing every time I tried to pair a phone to it. I did want to try out the new KDE plasma 5, since it's been a few years since I used KDE, but I mainly wanted this KDE Connect app to work and use it with the MATE desktop, and it requires a lot of KDE packages to be installed for it to work. I loaded up an install of Linux Mint 20.04 and tried out KDE Connect with it. It downloaded about 1Gb of packages, but it worked perfectly first try with contacts, and replying to text messages. So I figure I have to some library files either missing or in the wrong place, or missing some packages totally. I tried to get KDE to work back with LFS 9.1/9.2 and never got it to fully work, apps would work, but not the plasma desktop environment. Then I rebuilt my system about a month ago and got KDE to work, and thought I'd give KDE connect another try... somewhere along the way I broke GDM temporarily, broke KDE plasma, completely removed KDE with kf5 5.72.0 and then rebuilt with kf5 5.73.0 and it worked again... Thanks, Tim > -- > http://lists.linuxfromscratch.org/listinfo/blfs-dev > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page
-- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
