[PATCH] kconfig_compiler and C++ file extensions
faure at kde.org
Tue Jan 13 14:13:02 GMT 2004
On Tuesday 13 January 2004 14:40, Adriaan de Groot wrote:
> On Tue, 13 Jan 2004, Chris Howells wrote:
> > On Tuesday 13 January 2004 13:24, Frans Englich wrote:
> > > I have no idea what files it's about nor what code, but can't you just move
> > > the files to .cpp equivalents?
> > Why? We don't try to enforce other coding styles (e.g. tabs/versus) spaces on
> > others (unless changing someone's already written code), so extensions should
> > be no different.
> Cutting off the thread now, as we're _waaaay_ into bikeshed territory by
> now. I retract my request to commit this now, since I just realized that
> 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.
> - 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?
David FAURE, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).
More information about the kde-core-devel