[CMake] CTEST_UPDATE for clearcase

Hi, CTEST_UPDATE doesn't officialy operate on ClearCase views, but would it be difficult to add support to CTEST_UPDATE just collecting config spec contents and sending it to CDash with subsequent CTEST_SUBMIT command ? Is Update.xml capable of containing such information as ClearCase config

Re: [CMake] Simultaneous --build-and-test and CDash submission

You can do it all in one step with ctest, but you have to write a ctest -S script, and call that... Inside it, you can do a configure from scratch using the ctest_configure(...) command. Then you'll see all the configure output submitted to the dashboard. Poke around the wiki and the

[CMake] Simultaneous --build-and-test and CDash submission

Hi, I have unit tests configured for CDash submissions. Submissions do work if I issue in sequence TWO commands which go pretty much like this: # configure the build system ${CMAKE_ROOT}${CMAKE_BINDIR}/cmake . # build tests make clean ; make # run tests ${CMAKE_ROOT}${CMAKE_BINDIR}/ctest

Re: [CMake] Simultaneous --build-and-test and CDash submission

So my question is how to achieve CDash submission with 'scratch' configure info (just as if cmake was invoked on clean environment), build info (compilation warnings and such) and test results by issueing single command ? Thanks for help, Wojtek Hi Wojtek, If I

Re: [CMake] Simultaneous --build-and-test and CDash submission

Użytkownik napisał(a): From: Subject: Re: [CMake] Simultaneous --build-and-test and CDash submission To: Wojciech Migda ; On Thu, Dec 9, 2010 at 4:13 AM, Wojciech Migda wrote: Hi, I have unit tests configured for CDash submissions. Submissions do work if I issue in sequence

[CMake] General LABELS questions

Hi, I'm trying to get LABELS/Subprojects working, having read this http://www.kitware.com/blog/home/post/11 and this http://www.kitware.com/blog/home/post/11 1. It is unclear to me whether to have LABELS working I must use CTest script (-S) or I can achieve that simply by editing of

[CMake] Merging gcc unit tests into a TI DSP crosscompiler build system

Hi, in our company we have a robust cmake-based build system which utilizes TI DSP cgtools compiler. Aside from that we are developing gcc-based unit tests (CxxTest coupled with CMake/CTest/CDash combo). We are considering merging the latter into the former, but we kind of don't even know how

Re: [CMake] CTest misses out with code coverage on files whose path is outside PROJECT_SOURCE_DIR

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wojciech Migda pisze: Hi, I have found a strange behaviour of ctest when performing code coverage analysis for unit tests. When the unit test binary is linked with a static library compiled from source files located outside

Re: [CMake] CTest - C Unit Testing Framework

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dixon, Shane pisze: !-- /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:Times New Roman;} a:link, span.MsoHyperlink {color:blue; text-decoration:underline;}

[CMake] CTest misses out with code coverage on files whose path is outside PROJECT_SOURCE_DIR

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I have found a strange behaviour of ctest when performing code coverage analysis for unit tests. When the unit test binary is linked with a static library compiled from source files located outside the PROJECT_SOURCE_DIR then although the *.gcov

Re: [CMake] Pass value from CMake to source file?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eric Noulard pisze: 2009/10/4 motes motes mort.mo...@gmail.com: Is it possible to send a user specified path from CMake to the final application (make it visible)? Depending on which machine I build my application on the path to some images may

[CMake] Disabling ranlib on *nix systems

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'd like to force CMake not to execute ranlib on *nix system. I've got a workaround - I set CMAKE_RANLIB to 'echo' - but it's nonelegant. Is there another way to disable execution of ranlib ? There is a reason why I need that: TI DSP linker for

[CMake] Dependencies resolution for generated assembler files (TI DSP, s62/h62)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, projects created using Texas Instruments DSP tools involve compilation of assembler source (*.s62) and header (*.h62) files generated using a dedicated tool (tconf). Those source files include headers using a directive of a form: .include

Re: [CMake] CMake 2.8.0 RC 1 ready for testing!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 and what about clearcase snapshot views updating ? Any plans ? Wojciech Michael Wild pisze: Usually I use cvs update -dARP which IMHO should probably be the default, because that's what people (i.e. me) expect from an update. Are there any

[CMake] Extending list of files subject to coverage with CTest

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, I am considering adding code coverage metrics to the executed unit tests. I get it work - I mean gcov i run and data is collected. However, from what I observed files subjected to coverage analysis is limited to those explicitly listed in the

Re: [CMake] Ctest and CxxTest

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Blezek pisze: We tackled this using a hack-ish CMake command for Google Tests that found all our tests in the source code, and generated CTest commands for them. You could do a similar thing on a test suite. Details are here:

[CMake] Ctest and CxxTest

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, I was wondering about an improvement for the way CxxTest unit tests are coupled with CTest. Right now when CTest submits results to CDash the tests are counted by binaries executed. In my unit tests each binary corresponds to an entire suite

Re: [CMake] Ctest and CxxTest

:01 AM, Wojciech Migda wojtek.g...@interia.pl wrote: Hi all, I was wondering about an improvement for the way CxxTest unit tests are coupled with CTest. Right now when CTest submits results to CDash the tests are counted by binaries executed. In my unit tests each binary corresponds

[CMake] OUTPUT_REQUIRED_FILES - how does it work ?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi again, while exploring possibilities to solve dependency problems I took a peek at the OUTPUT_REQUIRED_FILES command. I constructed simple CMakeLists.txt OUTPUT_REQUIRED_FILES( bar.c baz.txt ) ADD_LIBRARY( foo bar.c ) and the contents of bar.c

Re: [CMake] Generated source files and dependencies(+) (Wojciech Migda)

Użytkownik Clinton Stimpson napisał(a): From: Clinton Stimpson Subject: Re: [CMake] Generated source files and dependencies(+) (Wojciech Migda) To: cmake@cmake.org On Tuesday 08 September 2009 02:14:45 pm Wojciech Migda wrote: Why not include it in the foo target, instead of making

Re: [CMake] Generated source files and dependencies(+) (Wojciech Migda)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexander Neundorf pisze: On Tuesday 08 September 2009, Wojciech Migda wrote: Why not include it in the foo target, instead of making a new a_h_gen target and doing extra dependencies manually? Firstly, we have hundred of source files which may

[CMake] Generated source files and dependencies(+) (Wojciech Migda)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, some time ago there was a discussion, which has highlighted problem I am facing now, but it did not provide final conclusions (http://www.cmake.org/pipermail/cmake/2008-September/024093.html). Take this example: - --

Re: [CMake] Generated source files and dependencies(+) (Wojciech Migda)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Why not include it in the foo target, instead of making a new a_h_gen target and doing extra dependencies manually? Firstly, we have hundred of source files which may indirectly depend generated source files, so we want such information to be

[CMake] Cygwin performance

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, cygwin of known for its poor performance wrt some disc i/o operations. I'm already making some changes which will enhance cmake timings on cygwin, would you guys be interested receiving them, or maybe somebody from cmake team is already

Re: [CMake] Common binary dir and failed local headers dependencies

Bill Hoffman pisze: Wojciech Migda wrote: Hi again, this workaround seems to do a trick: in cmDependsC::WriteDependencies I've added a local variable to store path to the source file being scanned for dependencies: std::string root_dir = cmSystemTools::GetFilenamePath

[CMake] Common binary dir and failed local headers dependencies

Hi all, I have a build system with several subtargets residing in respective subfolders. What is important - I'm using common binary directory for all targets. The command I use is: ADD_SUBDIRECTORY( nth_subfolder common_binary_dir ) The common binary folder was chosen to have all static

Re: [CMake] Common binary dir and failed local headers dependencies

some follow-up to my previous post: I don't see an easy way to fix the presented problem within cmake scripting mechanisms other than adding own script called at the setup time for dependencies check and adding those dependencies to objects using SET_PROPERTIES* directives. However, as far as I

Re: [CMake] Common binary dir and failed local headers dependencies

team evaluate this proposal ? BR, Wojtek Wojciech Migda pisze: some follow-up to my previous post: I don't see an easy way to fix the presented problem within cmake scripting mechanisms other than adding own script called at the setup time for dependencies check and adding those dependencies

Re: [CMake] Unwanted quoting of $

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, | | I’ve run into a problem trying to pass command line parameters to Visual C++, that contain the $ character. I’m building a C++/CLI module, and need to reference some .NET assemblies, with the /FU compiler option. Since Visual Studio

Re: [CMake] ASM Cross Compiler Help

Hi, I see that there are some CMake modules that seem to be referring to ASM Compilers (I am assuming this is an assembly compiler) and the release notes for 2.6 seem to confirm this. I can't seem to find any information on how to configure it. I am setting up a cross-compiler environment and

Re: [CMake] File-dependent rebuild

I'd like to have cmake rebuild upon detecting changes made to a file being part of the project (simple timestamp difference might suffice). This file is not a compiler input itself, but is used to determine the list of source files upon which the library to build is dependant. The file of

[CMake] Dependencies handling vs. timestamp

Hi, does cmake support handling of a situation when the timestamp of the file upon which trigger for a given action is dependent (compilation, build system regeneration) moves to past? -Wojciech -- Sprawdz, czy jestes

Re: [CMake] CMAKE 2.6.0: Wrong dependencies when CMakeLANGInformation.cmake is missing

/ It's an embedded system with it's own proprietary OS. / own proprietary OS == you/your company wrote it or an RTOS one can buy ? Adding support for some commercial RTOS like e.g. VxWorks to cmake would be ok. Yes, it is our own RTOS, not publicly available. / Why do you need

[CMake] File-dependent rebuild

Hi, I'd like to have cmake rebuild upon detecting changes made to a file being part of the project (simple timestamp difference might suffice). This file is not a compiler input itself, but is used to determine the list of source files upon which the library to build is dependant. The file

Re: [CMake] CMAKE 2.6.0: Wrong dependencies when CMakeLANGInformation.cmake is missing

I've prepared a patch against the 2.6.0 version. Unfortunately I could not find the patch format instructions for cmake, so I took those for linux kernel (diff -up). Thanks for the patch. The asm support is still very new, so thanks for pointing out issues. Can you create a small test project

Re: [CMake] CMAKE 2.6.0: Wrong dependencies when CMakeLANGInformation.cmake is missing

Alexander Neundorf pisze: On Sunday 08 June 2008, Wojciech Migda wrote: As it appeared the . entry was present due to me using user-defined assembler compiler for the build. Commenting out the relevant ENABLE_LANGUAGE command in CMakeLists.txt led to proper behaviour. But why ? I looked

[CMake] CMAKE 2.6.0: Wrong dependencies when CMakeLANGInformation.cmake is missing

to have the same problem. With best regards, Wojciech Migda --- Sprawdz jak zdobyc zdrowy usmiech! Kliknij http://link.interia.pl/f1e26 ___ CMake mailing list CMake@cmake.org http