Commit 329ddf57 authored by Ismael Asensio's avatar Ismael Asensio Committed by Alexander Lohnau
Browse files

kcm/rules: Use the new KCM namespace for standalone launch

After commit c1d0aa18, the namespace where the KCM is installed
changed to `plasma/kcms/systemsettings/`.

We need to point to this new plugin location when the KCM is
launched via Alt-F3 > "Window Specific Properties"

Also let's set the full plugin location from CMake instead of
harcoded in C++ so it is easier to keep it in sync.

BUG: 454066
FIXED-IN: 5.25.0
parent 14aefcb3
Pipeline #179058 passed with stage
in 13 minutes and 3 seconds
......@@ -44,6 +44,7 @@ target_link_libraries(KWinRulesObjects ${kcm_libs} ${kwin_kcm_rules_XCB_LIBS})
add_executable(kwin_rules_dialog main.cpp)
target_link_libraries(kwin_rules_dialog KWinRulesObjects)
target_compile_definitions(kwin_rules_dialog PRIVATE KCMRULES_PLUGIN="plasma/kcms/systemsettings/kcm_kwinrules")
kcoreaddons_add_plugin(kcm_kwinrules SOURCES kcmrules.cpp INSTALL_NAMESPACE "plasma/kcms/systemsettings")
......@@ -50,7 +50,7 @@ int main(int argc, char *argv[])
kcm_args << QStringLiteral("whole-app");
KPluginMetaData pluginData = KPluginMetaData(QStringLiteral("kcms/kcm_kwinrules"));
KPluginMetaData pluginData = KPluginMetaData(QStringLiteral(KCMRULES_PLUGIN));
KCMultiDialog *dialog = new KCMultiDialog;
dialog->addModule(pluginData, kcm_args);
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment