[PATCH] kconfig_compiler and C++ file extensions
Adriaan de Groot
adridg at sci.kun.nl
Tue Jan 13 16:37:54 GMT 2004
On Tue, 13 Jan 2004, David Faure wrote:
> On Tuesday 13 January 2004 14:40, Adriaan de Groot wrote:
> > the new KConfigXT stuff that is causing the problem is in
> > osnabrueck_branch, so it's no problem to release KDE 3.2 with a no-XT
> > version of KPilot.
> > Post 3.2, I would like to add this feature
> Wrong thinking - you won't be able to release kdepim-3.3 if it depends on
> unreleased kdelibs changes.
OOh. I never claimed thinking was any good, did I?
> > - or figure out why/how
> > autoconf on my system wants .cc extensions for the kcfg files as well.
> am_edit or unsermake, not autoconf. Probably because there are already
> .cc files in that dir?
Yes. So that means that adding suffix support _is_ critical for 3.2 - or
am_edit needs more tricking out to ignore the existing C++ suffix in a
directory. Ugh. Well, I suppose "KConfigXT supports .cpp file extensions
only" and a big happy rename session would work as well.
Adriaan de Groot adridg at cs.kun.nl Kamer A6020 024-3652272
GPG Key Fingerprint 934E 31AA 80A7 723F 54F9 50ED 76AC EE01 FEA2 A3FE
More information about the kde-core-devel