After installing all the dependencies to get
kdesrc-build plasma-workspace to get 99% complete, I soon discovered that
networkmonitor-qt would not build since
libnm0 (managed by ubuntu) was
v1.2 in xenial.
I’d been meaning to try the Neon update to bionic so I figured why not upgrade it.
libnm0 in bionic is
v1.10 which should fix the dependency issue. (Update: Neon is now shipping bionic by default now)
libudev.so is missing
After upgrading to bionic flawlessly, I ran
kdesrc-build again. This time I ran into trouble with
kwin. Both build error logs mentioned:
apt search libudev shows that
libudev-dev are installed, so it’s not that.
apt show libudev1 showed that it’s part of systemd btw.
locate libudev.so had interesting output though.
It seems that it can’t find
/usr/lib/, but it did exist in
/lib. Well solid was compiling before the bionic upgrade, lets check my host OS KDE Neon User which is still on xenial.
So it looks like it’s got
/usr/lib/x86_64-linux-gnu/libudev.so, lets see which package owns it with
dpkg -S /usr/lib/x86_64-linux-gnu/libudev.so.
Welp. A glance at the file list on https://packages.ubuntu.com for xenial and bionic shows the removal of the
For now, I’ll try symlinking the file to the one in
kdesrc-build plasma-workspace will now build everything without errors, huzzah!
plasma-desktop needs over 3Gb RAM to build
Now I tried building a few more packages with
plasma-desktop. I first noticed it tried to rebuid everything
plama-workspace needed as well, before finally trying to build
plasma-desktop. After checking
kdesrc-build --help, I realized I’d need to run the following every time I wanted to build a single package.
For now though, lets build
plasma-desktop starting with
I ran into a new problem when building the
Turns out I was running out of RAM! This time I ran
kdesrc-build with KSysGuard open with the RAM graph visible.
Turns out building that package uses 1Gb more RAM than normal, climbing up to the max of 2Gb my VM is setup with. It also seems I forgot to properly setup the swap partition after resizing the partitions. Oops.
I first tried adding another gig of RAM to my VM, but even with 3Gb, it ran out.
So I formatted the swap and turned it on. Maybe it requires more RAM than normal if you build with 2 cpu cores.
After setting up the swap, everything built correctly.
The next step from building from source is appearently setting up a runtime environment. This involves creating a script that overrides a bunch of environment variables in the current Terminal session.
It mentions there’s extra steps for Plasma, but I was interested in what would happened if I run plasmashell now? Well I tested it with the following:
Suprisingly, everything loaded okay.