kconfig_compiler problem: no signals on changes

[Waldo Bastian]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri March 12 2004 16:04, Cornelius Schumacher wrote:
> 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.

It would be possible to do the splitting based on information in the .kcfgc 
file. But again, that would need to be implemented first, and since you want 
to build against KDE 3.2 that wouldn't help you.

Cheers,
Waldo
- -- 
bastian at kde.org -=|[ SUSE, The Linux Desktop Experts ]|=- bastian at suse.com

"IBM may, in any manner it sees fit and without royalty to SCO, 
 distribute any Licensed IBM Materials contained in the SCO Products"
From: Joint Development Agreement between the SCO, Inc. and
      International Business Machines Corporation
http://www.sec.gov/Archives/edgar/data/851560/0000891618-99-000561.txt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFAUegpN4pvrENfboIRAiinAJ9sLb02oobozMqKgJMLZ9OTpNXKUgCdEeok
Ay7lQ7Fh1BZwISD+KWXNpVE=
=JPpW
-----END PGP SIGNATURE-----