Re: [CMake] macro/functions in ctest scripts

-Original Message- From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of Yngve Inntjore Levinsen Sent: Donnerstag, 8. August 2013 17:54 Cc: cmake@cmake.org Subject: Re: [CMake] macro/functions in ctest scripts Den 08. aug. 2013 17:36, skrev Jakub Zakrzewski: > Hi,

Re: [CMake] Can CMake confgure shorter cmmand argments?

On Thu, 08 Aug 2013 17:42:17 -0400, Bill Hoffman wrote: >On 8/8/2013 4:14 PM, Bo Berglund wrote: >> Do you mean that I should start cmake from the command line and then >> configure and generate the project again? >> Should I clear the binary folder first to make a clean slate? >> Or can I keep t

[CMake] colored output from CTest

I'm a newbie to CTest. I've been successfully integrated CTest and GTest. But I wonder whether I could get colored output from CTest like things from gtest. Thanks. -- best, gongzhitaao-- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.o

Re: [CMake] Can CMake confgure shorter cmmand argments?

On 8/8/2013 4:14 PM, Bo Berglund wrote: Do you mean that I should start cmake from the command line and then configure and generate the project again? Should I clear the binary folder first to make a clean slate? Or can I keep the data already there and just make a new generate? You might get awa

Re: [CMake] Can CMake confgure shorter cmmand argments?

On Thu, 08 Aug 2013 11:31:48 -0400, Bill Hoffman wrote: >On 8/8/2013 1:45 AM, Bo Berglund wrote: >> tlib /p512 /a "..\..\..\bin\vtkhdf5.lib" >> "CMakeFiles\vtkhdf5.dir\H5.c.obj" >> "CMakeFiles\vtkhdf5.dir\H5checksum.c.obj" >> >> "CMakeFiles\vtkhdf5.dir\H5FDwindows.c.obj" >> "CMakeFi

Re: [CMake] macro/functions in ctest scripts

Den 08. aug. 2013 17:36, skrev Jakub Zakrzewski: > Hi, > > a neee - just ignore this - I need more sleep... > > This indeed looks like a correct piece of code. > Moreover - it works perfectly with my ctest... No problem. I noticed that if I add this in the "ctest run script", i.e. the script I exe

Re: [CMake] macro/functions in ctest scripts

Den 08. aug. 2013 17:32, skrev Matthew Woehlke: > That said, have you tried naming the variable other than the name of a > built-in command? I could imagine that might cause problems... Yes, I did not notice this problem by writing the hello world macro initially. My macro was something along the

Re: [CMake] macro/functions in ctest scripts

-Original Message- From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of Jakub Zakrzewski Sent: Donnerstag, 8. August 2013 15:24 To: Yngve Inntjore Levinsen; cmake@cmake.org Subject: Re: [CMake] macro/functions in ctest scripts -Original Message- From: cm

Re: [CMake] macro/functions in ctest scripts

On 2013-08-08 09:24, Jakub Zakrzewski wrote: On 2013-08-08 09:08, Yngve Inntjore Levinsen wrote: macro(hello MESSAGE) message("${MESSAGE}") endmacro(hello) hello("Hello World") This does not work (it gives a warning that the message command was called with wrong number of arguments). Howeve

Re: [CMake] Can CMake confgure shorter cmmand argments?

On 8/8/2013 1:45 AM, Bo Berglund wrote: tlib /p512 /a "..\..\..\bin\vtkhdf5.lib" "CMakeFiles\vtkhdf5.dir\H5.c.obj" "CMakeFiles\vtkhdf5.dir\H5checksum.c.obj" "CMakeFiles\vtkhdf5.dir\H5FDwindows.c.obj" "CMakeFiles\vtkhdf5.dir\__\H5Tinit.c.obj" "CMakeFiles\vtkhdf5.dir\__\H5lib_settings

[CMake] Feature Request: performing the "Configure" step but not Generation with cmake command line tool (as in cmake-gui and ccmake)

Hi, Sometimes ago I asked for the following feature with ID 0013359: The issue has been pushed back in the backlog. In the mean I added a patch. Recently I updated it with the last version of cmake in in git. I wonder if there was any space for this to be reviewed and in case integrated in the ma

Re: [CMake] add_test/memcheck

Am 08.08.2013 14:09, schrieb cabieces julien: Hi I'm currently using the simple way of testing in Cmake, just adding the two following instructions at the end of my CMakeLists.txt; enable_testing() add_test(TestMyProgram MyProgram) I follow this instruction : http://cmake.org/Wiki/CMake/Tes

Re: [CMake] macro/functions in ctest scripts

Den 08. aug. 2013 15:24, skrev Jakub Zakrzewski: > Hi, > >>> >>macro(hello MESSAGE) >>> >> message("${MESSAGE}") >>> >>endmacro(hello) >>> >>hello("Hello World") > You're expecting MESSAGE to be variable name but you call it with string > value. So > message("${MESSAGE}") > evaluates to > messa

Re: [CMake] macro/functions in ctest scripts

-Original Message- From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of Yngve Inntjore Levinsen Sent: Donnerstag, 8. August 2013 15:09 To: cmake@cmake.org Subject: [CMake] macro/functions in ctest scripts Hi, I have a project where we use ctest/cdash but not cmak

[CMake] How does CMake decide which compiler it should use?

I have one instance of C++Builder XE4 installed and when I run CMake it goes about testing the compiler before reaching the point where I can select any sources to generate makefiles for. But if I install two older versions of C++Builder in addition to the XE4 version, there will be 3 complete C++

[CMake] macro/functions in ctest scripts

Hi, I have a project where we use ctest/cdash but not cmake. I wanted to add a macro, but it looks like it doesn't support arguments correctly? (differing from the documentation in 'ctest --help-command macro') I tried to add this to the CTestTestfile.cmake: macro(hello MESSAGE) message("${ME

[CMake] add_test/memcheck

Hi I'm currently using the simple way of testing in Cmake, just adding the two following instructions at the end of my CMakeLists.txt; enable_testing() add_test(TestMyProgram MyProgram) I follow this instruction : http://cmake.org/Wiki/CMake/Testing_With_CTest and I would like to make memory ch

[CMake] ctest -j and PARALLEL_LEVEL argument

Hi, This one should be a super-quick: does "ctest -j N" also set a default PARALLEL_LEVEL=N for ctest_memcheck and ctest_test? Could not google anything useful out! Thanks in advance! This message has been sent from a Mediobanca S.p.A. email address. The informat

[CMake] Re: Re-running automoc all the time after #13494

Hi, is there a solution for automoc being re-run every time when the binary directory is in the include path (see below)? Cheers, Jan On Wednesday, 31 July 2013 11:43:48 CEST, Jan Kundrát wrote: Hi folks, I am using out-of-tree builds with Trojita [1], a Qt application. My cmake version is 2.