From 4c62867b4a38db28c29a063219b9d0f5c7f1cac6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dawid=20Wr=C3=B3bel?= Date: Fri, 26 Nov 2021 11:32:53 +0000 Subject: README.dox: GENERATE_MOC is required for signals --- src/kconfig_compiler/README.dox | 2 ++ 1 file changed, 2 insertions(+) (limited to 'src') 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 \, \ and \ element for an entry. -- cgit v1.2.1