KConfig XT: kconfig_compiler & friends

[Waldo Bastian]

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

> Is this stuff right to go in to 3.2? 

Yes, because otherwise we are stuck with KAutoConfig which is design-wise 
flawed.

> Also, if you let me know how one 
> should call kconfig_compiler, I'll write the relevant support for
> unsermake.

At the moment a pair of *.cpp/*.h files are built from a combination of *.kcfg 
and *.kcfg-codegen file. The idea is that the *.kcfg file describes the 
actual configuration entries while the *.kcfg-codegen file contains 
instructions for the code generation. This way a single *.kcfg file can be 
used to build different sets of *.cpp/*.h files from.

The idea is then that the *.kcfg-codegen file should be added to foo_SOURCES 
in Makefile.am

Assuming both a file foobar.kcfg-codegen and foo.kcfg, something like the 
following should then be added:

# avoid running the below command in parallel
foobar.cpp: foobar.h
foobar.cpp foobar.h: $(srcdir)/foo.kcfg $(srcdir)/foobar.kcfg-codegen
        kconfig_compiler $(srcdir)/foo.kcfg $(srcdir)/foobar.kcfg-codegen

I'm not sure how to specify foo.kcfg, ideally it should be possible to 
reference foo.kcfg files in other sub-directories and ones that are installed 
under $KDEDIR/share/config.kcfg

E.g. in kdebase/kcontrol/konsole one may wish to use kdebase/konsole/konsole.
kcfg

Maybe foobar.kcfg-codegen could contain a line like "kcfg=../konsole/konsole.
kcfg" or "kcfg=$KDEDIR/share/config.kcfg/konsole.kcfg" in such case.

Cheers,
Waldo
- -- 
bastian at kde.org -=|[ SUSE, The Linux Desktop Experts ]|=- bastian at suse.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE/ev4iN4pvrENfboIRAu4TAJoDmYLJjmMx7O29Tpkydy1xDS9bEgCeLL7F
H27KbV7NkfGJyDaP8621zsE=
=q/y4
-----END PGP SIGNATURE-----