[CMake] Running tests on a nomad cluster

Hi, We use cmake for one of our projects, which has ~400 tests. All in all, they take about an hour to run. What I’d like to do is to submit the tests as batch jobs on our nomad cluster. This part I can easily do, via some python script or go executable. What I’m not sure about is how to int

Re: [CMake] Running tests that depends on third-party DLL

Scott Aron Bloom writes: > I just ran into this exact problem. > > For me it was the TCL shared library, the technique I used worked fine > for windows and linux. > > Im not sure about OSX since you are running fixup_bundle.. > > I also used an ADD_CUSTOM_COMMAND, but I simply did a copy of the >

Re: [CMake] Running tests that depends on third-party DLL

, 2014 1:46 PM To: cmake@cmake.org Subject: [CMake] Running tests that depends on third-party DLL What is the best way to make tests that depend on a third-party DLL (found through `find_package`) work when run from the RUN_TESTS target? This scenario must be common so I surprised how hard it

[CMake] Running tests that depends on third-party DLL

What is the best way to make tests that depend on a third-party DLL (found through `find_package`) work when run from the RUN_TESTS target? This scenario must be common so I surprised how hard it seems to be to get it to work. Let's say I have a library project that depends on OpenSSL (just an ex

Re: [CMake] Running tests on remote machine

lready have an add_test wrapper. But if you do have a wrapper, it should be >> easy enough in theory. (Assuming you can drive a remote debugger session via >> a command line of some sort. Or via a script.) >> >> >> From: Robert Dailey >> Sent: March 19, 2013 3:3

Re: [CMake] Running tests on remote machine

Subject: Re: [CMake] Running tests on remote machine It simply uses TCP connection to the remote machine, using the Windows Remote Debugger service. it handles the details of remote debugging, all I do is point it to the correct executable to run from my project settings on the host machine. No

Re: [CMake] Running tests on remote machine

It simply uses TCP connection to the remote machine, using the Windows Remote Debugger service. it handles the details of remote debugging, all I do is point it to the correct executable to run from my project settings on the host machine. No authe The only thing that the program needs on the VM i

Re: [CMake] Running tests on remote machine

2013/3/18 Robert Dailey : > Hi, > > I currently have a VM that I use to debug my executables. It has the > environment setup that is needed by the programs. Naturally, the tests > also depend on this environment (nothing was really mocked). > > The machine hosting the VM is my dev machine, it only

[CMake] Running tests on remote machine

Hi, I currently have a VM that I use to debug my executables. It has the environment setup that is needed by the programs. Naturally, the tests also depend on this environment (nothing was really mocked). The machine hosting the VM is my dev machine, it only has CMake & Visual Studio. I set it up

Re: [CMake] Running tests only on modified projects....

David, Thank you for your response. -Kris -Original Message- From: David Cole [mailto:david.c...@kitware.com] Sent: Tuesday, April 10, 2012 1:28 PM To: Malfettone, Kris Cc: cmake@cmake.org Subject: Re: [CMake] Running tests only on modified projects It is presently not

Re: [CMake] Running tests only on modified projects....

ake.org] On Behalf Of > Malfettone, Kris > Sent: Tuesday, March 27, 2012 10:11 AM > To: cmake@cmake.org > Subject: [CMake] Running tests only on modified projects > > > > I’ve been looking through the ctest documentation and online for a while now > and can’t see

Re: [CMake] Running tests only on modified projects....

: [CMake] Running tests only on modified projects I've been looking through the ctest documentation and online for a while now and can't seem to find a way to run tests only from projects that have changed. Basically what I have is a very large build tree consisting of many projec

[CMake] Running tests only on modified projects....

I've been looking through the ctest documentation and online for a while now and can't seem to find a way to run tests only from projects that have changed. Basically what I have is a very large build tree consisting of many projects. When someone submits code to just one of the projects I wou

Re: [CMake] Running tests using [C++/Python] modules from the build tree

Hi Marcel, > You could write a wrapper script that sets your environment variables. > Since you don't know the actual values for these variables beforehand, > you should let CMake generate this script, using configure_file(). > That's the way I do it, and it works great. Thanks for the suggestio

Re: [CMake] Running tests using [C++/Python] modules from the build tree

On Tue, 2010-09-28 at 18:42 +0200, Pere Mato Vila wrote: > Hi, > > I am seeking for advise. I would like to run some CTest tests from the build tree, which require C++ or Python modules created in other project directories (packages). For this I need to build correctly the LD_LIBRARY_PATH and PY

[CMake] Running tests using [C++/Python] modules from the build tree

Hi, I am seeking for advise. I would like to run some CTest tests from the build tree, which require C++ or Python modules created in other project directories (packages). For this I need to build correctly the LD_LIBRARY_PATH and PYTHONPATH and use the command set_property(TEST xxx PROPERTY

Re: [CMake] Running tests as part of a build

2010/1/10 Dmytro Ovdiienko > Gavin, > > Good practice is to run as much tests as possible and do not stop on first > failed test. > > Hi Dmytro, Thank you for your advice. For integration or overnight build testing I absolutely agree, and that is where I could use "make test" to run full tests

Re: [CMake] Running tests as part of a build

Gavin, Good practice is to run as much tests as possible and do not stop on first failed test. 2010/1/8 Gavin Heavyside > Have you looked at add_custom_command(TARGET ...) or >> add_custom_target(...)? >> Those are how you run can run commands as part of the build, but after >> some >> other t

Re: [CMake] Running tests as part of a build

> > Have you looked at add_custom_command(TARGET ...) or > add_custom_target(...)? > Those are how you run can run commands as part of the build, but after some > other targets are compiled. > > Clint > That works great, thanks for the tip! I build my code, and then my test programs using add_exe

Re: [CMake] Running tests as part of a build

On Friday 08 January 2010 11:10:23 am Gavin Heavyside wrote: > I am seriously looking at moving the build system of some existing software > from scons to cmake. Most things I want to accomplish seem easier in > cmake, but there is one thing I can't work out how to do. > > I like to have (at least

[CMake] Running tests as part of a build

I am seriously looking at moving the build system of some existing software from scons to cmake. Most things I want to accomplish seem easier in cmake, but there is one thing I can't work out how to do. I like to have (at least some) unit test run as part of the build, e.g. when I type 'make' the

[CMake] Running tests

Hi all, Maybe it is a simple question, but I really have no answer. So, hope you could help me. Here is my directories tree : |_ src __ | |_ geometrie | |_ truc | |_ test __ |_ geometrie |_ truc In test, I have this CMakeLists.txt :