You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It results in an empty string for the install prefix because --install-prefix is not a valid option for kf5-config. This is what happens as a result:
$ make install
[ 16%] Built target eu.naraesk.docker-control-plasmoids-metadata-json
[ 33%] Automatic MOC for target plasmoidplugin
[ 33%] Built target plasmoidplugin_autogen
[100%] Built target plasmoidplugin
Install the project...
-- Install configuration: "Release"
-- Installing: /share/plasma/plasmoids/eu.naraesk.docker-control
CMake Error at cmake_install.cmake:41 (file):
file INSTALL cannot make directory
"/share/plasma/plasmoids/eu.naraesk.docker-control": No such file or
directory
Makefile:117: recipe for target 'install' failed
make: *** [install] Error 1
I couldn't figure out the option/argument for kf5-config to get the correct install prefix, so I hardcoded it:
This caused the plasmoid to be installed in the correct location. However, it tries to install some stuff in a location that requires root access. Is this avoidable?
Thanks for reporting. It must be kf5-config --prefix instead of kf5-config --install-prefix. Usually, this is /usr. I'm about releasing version 2.0 of this plasmoid with new features within the next days. I will have a look if a complete local installation is possible.
This plasmoid installs a plugin for qml to access docker from qml. As far as I know, something like user specific qml plugins do not exist, therefore it is not possible to install it home directory.
OS: Kubuntu 18.04
This is the
cmake
command from README.md.:It results in an empty string for the install prefix because
--install-prefix
is not a valid option forkf5-config
. This is what happens as a result:I couldn't figure out the option/argument for
kf5-config
to get the correct install prefix, so I hardcoded it:This caused the plasmoid to be installed in the correct location. However, it tries to install some stuff in a location that requires root access. Is this avoidable?
The text was updated successfully, but these errors were encountered: