[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: [PATCH] kconfig_compiler and C++ file extensions
From:       Frans Englich <frans.englich () telia ! com>
Date:       2004-01-12 19:28:34
Message-ID: 200401122028.34970.frans.englich () telia ! com
[Download RAW message or body]

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? 


			Frans

[prev in list] [next in list] [prev in thread] [next in thread]