aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDawid Wróbel <me@dawidwrobel.com>2021-11-26 11:32:53 +0000
committerDawid Wróbel <me@dawidwrobel.com>2021-11-26 11:32:53 +0000
commit4c62867b4a38db28c29a063219b9d0f5c7f1cac6 (patch)
tree669dc1a2400fd25b5b12032bd14def8d433ae9d8
parente40531e29e2ff52d67156aa8ae7691488ca1c29b (diff)
downloadkconfig-4c62867b4a38db28c29a063219b9d0f5c7f1cac6.tar.gz
kconfig-4c62867b4a38db28c29a063219b9d0f5c7f1cac6.tar.bz2
README.dox: GENERATE_MOC is required for signals
-rw-r--r--src/kconfig_compiler/README.dox2
1 files changed, 2 insertions, 0 deletions
diff --git a/src/kconfig_compiler/README.dox b/src/kconfig_compiler/README.dox
index 4c22a452..0ead5939 100644
--- a/src/kconfig_compiler/README.dox
+++ b/src/kconfig_compiler/README.dox
@@ -531,6 +531,8 @@ for a signal, the signal name will suffice.
You can also use the generic configChanged() signal from KConfigSkeleton to notify your application
about configuration changes.
+Note that you will also need to pass the GENERATE_MOC option to the kconfig_add_kcfg_files macro.
+
\subsection translation_context Translation context
In the kcfg file you can specify the translation's context for \<tooltip\>, \<whatsthis\> and \<label\> element for an entry.