kconfig_compiler problem: no signals on changes

Cornelius Schumacher schumacher at kde.org
Fri Mar 12 15:04:08 GMT 2004

On Friday 12 March 2004 15:17, Richard Smith wrote:
> One question, though: is there any easy way we can avoid having one .kcfg
> file for each block of options? Is it possible to have, for each group
> within the .kcfg file, a separate class being generated? If not, it's not
> insurmountable; we can add an extra pre-build step to split our kopete.kcfg
> up into chunks.

You currently need one kcfg file per generated class. I think this is 
consistent with the way we usually do it for C++ sources, one class per 
source file.

Cornelius Schumacher <schumacher at kde.org>

More information about the kde-core-devel mailing list