On Wed, Oct 13, 2010 at 22:21, Alexander Neundorf
wrote:
> CMAKE__SOURCE_FILE_EXTENSIONS is used quite early in the
> enable-language process, i.e. when the
> CMakeFiles/CMakeCompiler.cmake file is generated.
> If the variable is changed after that happened, it doesn't have an effect
> anymore.
T
On Tuesday 12 October 2010, Jed Brown wrote:
> On Tue, Oct 12, 2010 at 15:33, Michael Wild wrote:
> > set(SRCS src1.c src2.c src3.c)
> > set_source_files_properties(${SRCS} PROPERTIES LANGUAGE CXX)
> > add_executable(strange_beast ${SRCS})
>
> I can do that, but what's the point of the extension-b
On Tue, Oct 12, 2010 at 15:33, Michael Wild wrote:
> set(SRCS src1.c src2.c src3.c)
> set_source_files_properties(${SRCS} PROPERTIES LANGUAGE CXX)
> add_executable(strange_beast ${SRCS})
>
I can do that, but what's the point of the extension-based mapping if you
have to set properties by file?
On 12. Oct, 2010, at 15:26 , Jed Brown wrote:
> I realize this may look silly, but after
>
> list (REMOVE_ITEM CMAKE_C_SOURCE_FILE_EXTENSIONS c)
> list (APPEND CMAKE_CXX_SOURCE_FILE_EXTENSIONS c)
>
> source files matching *.c are still compiled with the C compiler (not C++).
> Is there a way
On 10/12/2010 03:26 PM, Jed Brown wrote:
> I realize this may look silly, but after
>
> list (REMOVE_ITEM CMAKE_C_SOURCE_FILE_EXTENSIONS c)
> list (APPEND CMAKE_CXX_SOURCE_FILE_EXTENSIONS c)
>
> source files matching *.c are still compiled with the C compiler (not C++).
> Is there a way to g
I realize this may look silly, but after
list (REMOVE_ITEM CMAKE_C_SOURCE_FILE_EXTENSIONS c)
list (APPEND CMAKE_CXX_SOURCE_FILE_EXTENSIONS c)
source files matching *.c are still compiled with the C compiler (not C++).
Is there a way to get *.c compiled with the C++ compiler?
(cmake-2.8.2)
