[PATCH] kconfig_compiler and C++ file extensions
frans.englich at telia.com
Mon Jan 12 19:28:34 GMT 2004
On Monday 12 January 2004 16:49, Adriaan de Groot wrote:
> Some nasty corner of kde-pim uses .cc as an extension for C++ files, while
> kconfig_compiler produces .cpp files. This wouldn't be a problem, except
> my auto* setup (autoconf 2.57, automake 1.7.5), when confronted with lists
> of sources with .cc extensions, decides that the compiled name of the
> .kcfg file will be .cc as well. And then the compilation fails, because
> the kcfg output is in a .cpp file.
Why do we want choice between *.cc and *.cpp? Wouldn't it be best if we all
just settled for one extension?
More information about the kde-core-devel