Re: [CMake] TEST_BIG_ENDIAN fails for a CXX project

I don't think the test should enable the C language, at least not for the entire project because that might cause weird and unexpected problems. It would be nice if the module could look at whether the C language or the C++ language were enabled (or both) and select the appropriate compiler for the

Re: [CMake] conflicting types for built-in function 'snprintf'

On Wednesday 08 July 2009, Steven Van Ingelgem wrote: > Hi, > > > I tried this call: > CHECK_FUNCTION_EXISTS(snprintf HAS_snprintf) > > > Which results in this error being generated: > C:\MinGW\bin\gcc.exe -g -ggdb -O0 -Wall -Werror > -DCHECK_FUNCTION_EXISTS=snprintf -o > CMakeFiles\cmTryCompi

Re: [CMake] Performance difference between SET and LIST ?

On Wednesday 08 July 2009, alexandre.feb...@thomsonreuters.com wrote: > Hi, > > with a very long list, is there a performance difference between using > SET and LIST to just declare a variable ? > > SET (var > val1 > val2 > ... > val2000) > > or > > SET(var) > LIST(APPEND var > val1 > val2 > ... >

[CMake] Performance difference between SET and LIST ?

Hi, with a very long list, is there a performance difference between using SET and LIST to just declare a variable ? SET (var val1 val2 ... val2000) or SET(var) LIST(APPEND var val1 val2 ... val2000) Thanks Regards, Alexandre Feblot This email was sent to y

Re: [CMake] itk configuration issue jar not created

neel vinoth wrote: Hi, Document available in net :GS-Java_Wrapping_in_ITK_VTK-v2.2.pdf Except Cmake version and visual studio version other files used as per the document. cmake-2.6.4-win32-x86.exe Visual Studio 6. Vtk compilation everythg ok Itk build failed with following error.

Re: [CMake] How to avoid -${MAKEFLAGS} in the CMAKE generated Makefiles ?

Xiangyun Kong wrote: Thanks. I am not sure how to ask CMAKE create unix makefiles on windows. cmake -G"Unix Makefiles" or when you run cmake-gui select "Unix Makefiles". You must be selecting "NMake Makefiles" somehow, so you do the same thing... -Bill

Re: [CMake] conflicting types for built-in function 'snprintf'

2009/7/8 Hendrik Sattler : > Zitat von Eric Noulard : >> >> It works for me and the CMakeFiles/CMakeOutput.log reads: >> >> Building C object CMakeFiles/cmTryCompileExec.dir/CheckFunctionExists.c.o >> /usr/bin/gcc  -DWHAT=ever -DCHECK_FUNCTION_EXISTS=snprintf >> -fno-builtin   -o >> CMakeFiles/cmTr

Re: [CMake] conflicting types for built-in function 'snprintf'

Probably I did something wrong than: C:\tmp\CMCheckWhatEver>cmake . -G"MinGW Makefiles" -- The C compiler identification is GNU -- Check for working C compiler: C:/MinGW/bin/gcc.exe -- Check for working C compiler: C:/MinGW/bin/gcc.exe -- works -- Detecting C compiler ABI info -- Detecting C comp

Re: [CMake] conflicting types for built-in function 'snprintf'

Zitat von Eric Noulard : It works for me and the CMakeFiles/CMakeOutput.log reads: Building C object CMakeFiles/cmTryCompileExec.dir/CheckFunctionExists.c.o /usr/bin/gcc -DWHAT=ever -DCHECK_FUNCTION_EXISTS=snprintf -fno-builtin -o CMakeFiles/cmTryCompileExec.dir/CheckFunctionExists.c.o -c /

Re: [CMake] conflicting types for built-in function 'snprintf'

2009/7/8 Eric Noulard -fno-builtin is not a definition, and try_compile (following the cmake docs) will add it to "add_definitions()", maybe it will work, but I think that's also not a very clean solution ;). I tried your solution, but I didn't see the parameter added into the error log... So I t

Re: [CMake] conflicting types for built-in function 'snprintf'

2009/7/8 Steven Van Ingelgem : > Hi Eric, > > > 1) Your first option wouldn't work because "CMAKE_REQUIRED_FLAGS" isn't > known by neither try_compile, neither the macro. Did you try it? The documentation says: CheckFunctionExists macro which checks if the function exists CHECK_FU

Re: [CMake] conflicting types for built-in function 'snprintf'

Hi Eric, 1) Your first option wouldn't work because "CMAKE_REQUIRED_FLAGS" isn't known by neither try_compile, neither the macro. 2) Wouldn't work either because try_compile doesn't take command line parameters (at least not in this form & unless you will construct the makefile from hand inside

Re: [CMake] conflicting types for built-in function 'snprintf'

2009/7/8 Steven Van Ingelgem : > Hi, > > > I tried this call: > CHECK_FUNCTION_EXISTS(snprintf  HAS_snprintf) > > > Which results in this error being generated: > C:\MinGW\bin\gcc.exe   -g -ggdb -O0 -Wall -Werror > -DCHECK_FUNCTION_EXISTS=snprintf   -o > CMakeFiles\cmTryCompileExec.dir\CheckFunctio

Re: [CMake] ctest & config type

Unfortunately, you've stumbled across a hole in the implementation. It should work the way you think it should work. :-) It's related to this bug: http://public.kitware.com/Bug/view.php?id=2336 As noted in that bug report, you may be able to work around this by setting the env var CMAKE_CONFIG_TY

Re: [CMake] Complete Path of source files being displayed in obj Files

2009/7/8 Malhotra, Anupam : > Hi David > > > > Thanks for the reply. I am not concerned about the names of object files. I > was talking about the contents of the object files. If you analyze the > object files, they contain the complete paths of corresponding source files. > This complete path is

[CMake] conflicting types for built-in function 'snprintf'

Hi, I tried this call: CHECK_FUNCTION_EXISTS(snprintf HAS_snprintf) Which results in this error being generated: C:\MinGW\bin\gcc.exe -g -ggdb -O0 -Wall -Werror -DCHECK_FUNCTION_EXISTS=snprintf -o CMakeFiles\cmTryCompileExec.dir\CheckFunctionExists.c.obj -c "C:\Program Files\CMake 2.7\sh

Re: [CMake] TEST_BIG_ENDIAN fails for a CXX project

2009/7/8 : > Hi! I have a project specified as CXX explicitly, and it requires knowing > the endian of the machine. I can't seem to use the TEST_BIG_ENDIAN module, > because it's a .c compilation and I get a > > ... /CheckIncludeFile.c".  TRY_COMPILE only works for enabled languages. > Currently e

Re: [CMake] help using try_run with custom build type

Hi Denis, On Wed, Jul 8, 2009 at 2:29 AM, Denis Scherbakov wrote: > >> > It appears to fail because the compiler options do not >> make it in when >> > creating the executable ... is there something silly I >> have missed? >> > Also, I was wondering why TRY_RUN doesn't use the >> default flags >>

[CMake] itk configuration issue jar not created

Hi,   Document available in net :GS-Java_Wrapping_in_ITK_VTK-v2.2.pdf   Except Cmake version and visual studio version other files used as per the document.   cmake-2.6.4-win32-x86.exe   Visual Studio 6.   Vtk compilation everythg ok   Itk build failed with following error.   Configuration: SwigRu

Re: [CMake] help using try_run with custom build type

> > It appears to fail because the compiler options do not > make it in when > > creating the executable ... is there something silly I > have missed? > > Also, I was wondering why TRY_RUN doesn't use the > default flags > > defined from CMAKE_BUILD_TYPE ? > Is this a bug or am I not using TRY_R