Registered Member
|
After a bit more investigation the major difference I can find between what works and what doesn't is that the 'installed' version has shared objects in
~/kde/lib/x86_64-linux-gnu/ with sub folder for plugins while the build version (the one that works) has all shared objects under the build/bin folder Maybe somebody can post their output of 'env' together with the folder structure for amarok Thanks Leo |
Registered Member
|
Now that I figured out the the cmake flag for debug is '-DCMAKE_BUILD_TYPE=Debug' and not '-DCMAKE_BUILD_TYPE=debugfull' I can now use gdb
Running gdb for ~/kde/bin/amarok shows
While running gdb for ~/kde/bin/amarok shows
|
Manager
|
IIUC, you did install locally in the ~/kde/build/amarok folder, so of course it will only run if run from this folder, unless you specified another target in your cmake line. Did I miss something?
Running Kubuntu 22.10 with Plasma 5.26.3, Frameworks 5.100.0, Qt 5.15.6, kernel 5.19.0-23 on Ryzen 5 4600H, AMD Renoir, X11
FWIW: it's always useful to state the exact Plasma version (+ distribution) when asking questions, makes it easier to help ... |
Registered Member
|
My cmake is
cmake -DCMAKE_INSTALL_PREFIX=$HOME/kdedev -DCMAKE_BUILD_TYPE=Debug -j4 -DCMAKE_VERBOSE_MAKEFILE=TRUE $HOME/kdedev/src/amarok I assume that 'things' (bin, lib, share,...) end up under $HOME/kdedev for 'make install' which they do
my $HOME/.kde/env/myenv.sh looks like this
I've also defined
my env before I start cmake and make is
|
Registered Member
|
Given that I can't do much right now without the embededd mysql (see my other post) I've gone back to the VM that was upgraded from 18.
I think I found out why the plugins are not found By default, the cmake script does not (seem) to generate a prefix.sh file. The content of this file for me are
So what seems to be missing from the intructions on how to get things working is the QT_PLUGIN_PATH & QML2_IMPORT_PATH Once these 2 paths are defined everything works as expected My cmake now looks as follows
|
Manager
|
wow, perfect, I will link this post to the amarok-devel mailing list.
Running Kubuntu 22.10 with Plasma 5.26.3, Frameworks 5.100.0, Qt 5.15.6, kernel 5.19.0-23 on Ryzen 5 4600H, AMD Renoir, X11
FWIW: it's always useful to state the exact Plasma version (+ distribution) when asking questions, makes it easier to help ... |
Registered Member
|
I've now also got amarok compiling and running in QT Creator.
I probably should start a new Howto (before I forget) and before I start working on amarok |
Registered Member
|
I had the same issue today.
It seems to be caused by the location where the plugins are installed, which is xxx/lib/plugins As a default Qt (or maybe Qt5, it could have changed) does not look into this folder. (see https://doc.qt.io/qt-5/deployment-plugins.html) It looks however in the application folder. This is why starting amarok from the build folder works as at that time the plugins are located at the same place. I checked by adding a debug output to the PluginManager. Only two directories, the Qt default and the application folder, are searched. You can set some environment variables (see the Qt link) to fix this.. How was this supposed to work? What do people with a working installation do different? |
Registered Member
|
Just tried it.
Setting QT_PLUGIN_PATH to the plugin path (~/kde/lib/amarok/plugins) helped. |
Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]