Hi everyone, i have the following code:
nclude(CMakePrintHelpers)
## MACROS
###
macro(bsIsInListBefore)
message(STATUS "bsIsInListBefore(): #${ARGV0}#${ARGV1}")
set(index1 0)
set(index2 0)
cmake_print_variables(ARG1)
l
- Mail original -
> De: "Mario Werner"
> À: cmake@cmake.org
> Envoyé: Vendredi 12 Janvier 2018 09:38:50
> Objet: Re: [CMake] test depending on code compilation
>
> On 2018-01-11 18:03, Franck Houssen wrote:
> >
> >
> > - Mail origina
On 2018-01-11 18:03, Franck Houssen wrote:
>
>
> - Mail original -
>> De: "Mario Werner"
>> À: cmake@cmake.org
>> Envoyé: Jeudi 11 Janvier 2018 16:27:18
>> Objet: Re: [CMake] test depending on code compilation
>>
> [snip]
>
>>
- Mail original -
> De: "Mario Werner"
> À: cmake@cmake.org
> Envoyé: Jeudi 11 Janvier 2018 16:27:18
> Objet: Re: [CMake] test depending on code compilation
>
> On 2018-01-10 10:47, Franck Houssen wrote:
> > [snip]
> >
> > The 2 unexpected
On 2018-01-10 10:47, Franck Houssen wrote:
> [snip]
>
> The 2 unexpected problems I have left are:
> 1) mytestexe is compiled everytime I type "make" which is a solution but
> is not really what I am looking for (also compiled when I type "make
> check" which is expected).
> => is there a way
OK, so I guess there is no way to do that like with autotools...
- Mail original -
> De: "Franck Houssen"
> À: "CMake Mail List"
> Envoyé: Mercredi 10 Janvier 2018 12:22:39
> Objet: Re: [CMake] test depending on code compilation
> I tr
d 0.00 sec
I want make test to run test only => OK and verbose is OK.
- Mail original -
> De: "Franck Houssen"
> À: "CMake Mail List"
> Envoyé: Mercredi 10 Janvier 2018 10:47:34
> Objet: [CMake] test depending on code compilation
> I need to d
I need to design a test (= a bash script) such that :
1) run a dedicated executable for the test (to be compiled)
2) diff the run output with a reference log file
The test is created with : add_test(mytest ./mytest.sh). The bash script would
look like:
>> more mytest.sh
/path/to/mytestexe >
Hello,
I am trying to get ctest working on CircleCI with multiple concurrent
containers. The following command works for many cases:
ctest -j 2 -I ${CIRCLE_NODE_INDEX},,${CIRCLE_NODE_TOTAL}
unless there are dependencies specified between tests via something like:
set_property(TEST B APPEND
Hi,
May be to include the module before using it:
include (TestBigEndian)
On 13/01/16 15:25, "CMake on behalf of Vania Joloboff" wrote:
>Hi
>
>I am familiar with autoconf and trying to migrate our project to cmake.
>Thus newbie. I am running cmake 3.2.2 on Linux Mint 17
>
>I have seen in t
Hi
I am familiar with autoconf and trying to migrate our project to cmake.
Thus newbie. I am running cmake 3.2.2 on Linux Mint 17
I have seen in the documentation the macro
https://cmake.org/cmake/help/v3.2/module/TestBigEndian.html?highlight=endian#module:TestBigEndian
which seems very conveni
-Ursprüngliche Nachricht-
Von:Nils Gladitz
Gesendet: Mo 12.05.2014 12:14
Betreff:Re: AW: [CMake] Test Shared Library Dependencies and
set_tests_properties()
An: Jörg Kreuzberger ;
> On 05/12/2014 11:59 AM, Jörg Kreuzberger wrote:
> > Hi!
> >
>
On 05/12/2014 09:10 AM, Jörg Kreuzberger wrote:
For execution i therefore call set_test_properties( testname PROPERTIES
ENVIRONMENT )
with LD_LIBRARY_PATH on Linux and PATH for windows. This seems to work on linux for
"cached" entries like e.g. ${QT_LIBRARY_DIR} or others. If i want to add to
Hi!
For using tests those tests have sometimes dependencies to shared libraries,
from cache and from build.
For execution i therefore call set_test_properties( testname PROPERTIES
ENVIRONMENT )
with LD_LIBRARY_PATH on Linux and PATH for windows. This seems to work on linux
for "cached" entries
Hi,
I can check if a target has been created:
add_custom_target(foo ...)
if (TARGET foo)
...
But I can't test for if an output rule has been created for foo.x:
add_custom_command(OUTPUT foo.x)
if (... foo.x)
Or is it possible ?
x.
--
Powered by
Thanks to all for the feedback / suggestions.
I did edit the wiki -- feel free to revise my submission or extend with
your own. I linked to this thread on there, as well.
http://www.itk.org/Wiki/CMake/Examples#Check_if_environment_variable_is_set
On Fri, Sep 14, 2012 at 4:43 PM, Bogdan Cristea
On Friday 14 September 2012 16:26:10 you wrote:
> On Fri, Sep 14, 2012 at 4:17 PM, Bogdan Cristea wrote:
> > On Friday 14 September 2012 16:13:16 Davis Ford wrote:
> >> if("$ENV{FOO_HOME}" MATCHES "")
> >>
> >>message("You must set FOO_HOME")
> >>return()
> >>
> >> endif()
> >
> > Try s
gt; Sent: Friday, September 14, 2012 3:26 PM
> To: Bogdan Cristea
> Cc: cmake@cmake.org
> Subject: Re: [CMake] Test if ENV${VAR} is set
>
> On Fri, Sep 14, 2012 at 4:17 PM, Bogdan Cristea wrote:
> > On Friday 14 September 2012 16:13:16 Davis Ford wrote:
> >> if(&quo
On Fri, Sep 14, 2012 at 4:17 PM, Bogdan Cristea wrote:
> On Friday 14 September 2012 16:13:16 Davis Ford wrote:
>> if("$ENV{FOO_HOME}" MATCHES "")
>>message("You must set FOO_HOME")
>>return()
>> endif()
>
> Try something like this
>
> if(NOT ENV{FOO_HOME})
> message("etc")
> endif()
>
> -
On Friday 14 September 2012 16:13:16 Davis Ford wrote:
> if("$ENV{FOO_HOME}" MATCHES "")
>message("You must set FOO_HOME")
>return()
> endif()
Try something like this
if(NOT ENV{FOO_HOME})
message("etc")
endif()
--
Bogdan
--
Powered by www.kitware.com
Visit other Kitware open-source
Hi, I'm new to CMake -- trying to do something relatively simple. Not
having much luck -- I've scoured the docs/wiki, but searching the manual
http://cmake.org/cmake/help/v2.8.9/cmake.html in the browser results in a
million hits for a search string.
I just want to test if an environment variable
Hi Kent,
Given the fact the parameter -R accepts a regular expression, you could use
the "^" and "$" associated with regular expression.
In your case, running:
ctest -R ^Foo$
will only execute test matching "Foo" where as running
ctest -R Foo
will execute tests having the string Foo wit
Here's something I find really annoying: Someone who names tests such
that the name of one is a prefix of the name of another! So if you do
this:
ctest -V -R
You get every test whose name begins with .
Just had to vent.
--
Powered by www.kitware.com
Visit other Kitware open-source projects
Thanks for the suggestion. It works with a more recent version.
On May 29, 2012, at 3:14 PM, Rolf Eike Beer wrote:
> Pere Mato Vila wrote:
>> No. Are you aware of any fix in this area? Changing the version in these
>> centrally maintained servers we are using is not immediate and I would like
Pere Mato Vila wrote:
> No. Are you aware of any fix in this area? Changing the version in these
> centrally maintained servers we are using is not immediate and I would like
> to make sure that my request is well justified. Cheers,
You can download a precompiled version from Kitware and extract i
No. Are you aware of any fix in this area? Changing the version in these
centrally maintained servers we are using is not immediate and I would like to
make sure that my request is well justified.
Cheers,
Pere
On May 29, 2012, at 1:40 PM, Rolf Eike Beer wrote:
> A
Am Dienstag, 29. Mai 2012, 09:38:53 schrieb Pere Mato Vila:
> When displaying the test results with CDash 2.0.2 produced by CTest 2.8.2,
> the output, which includes the building of the test, is truncated on the
> first occurrence of a compilation warning. The first character not
> displayed is [
When displaying the test results with CDash 2.0.2 produced by CTest 2.8.2, the
output, which includes the building of the test, is truncated on the first
occurrence of a compilation warning. The first character not displayed is [`].
An example of the results can be seen at
http://cdash.cern.c
Hi,
I want some help to organize tests within cmake.
Currently I have a test directory which contains some test files, eg :
test_foo.cpp
test_bar.cpp
In the CMakeLists.txt, I had:
add_executable(test_foo test_foo.cpp)
add_test(test_foo test_foo)
add_executable(test_bar test_bar.cpp)
add_test(tes
CMake 2.8.5, Debian Linux
I have tests in two different directories; the tests in one directory depend
on one test that is found in another directory.
If I try to test using 'make test', the tests run. Same for a ctest -S
script that doesn't use labels, and a script that runs all tests in the
pro
On 07/15/2011 03:15 AM, Clifford Yapp wrote:
> Is there a way to test flags supplied to the linker
> (CMAKE_SHARED_LINKER_FLAGS) in the same way we can test compiler flags
> with CHECK_C_COMPILER_FLAG? I'd like to check if -Wl,--no-undefined
> works or not before using it.
>
> Cheers,
> CY
You m
Is there a way to test flags supplied to the linker
(CMAKE_SHARED_LINKER_FLAGS) in the same way we can test compiler flags
with CHECK_C_COMPILER_FLAG? I'd like to check if -Wl,--no-undefined
works or not before using it.
Cheers,
CY
___
Powered by www.ki
The /usr/bin/file command on linux can be used to check the file type.
~> file /usr/lib/libpython2.6.so
/usr/lib/libpython2.6.so: symbolic link to `libpython2.6.so.1'
~> file /usr/lib/libpython2.6.so.1
/usr/lib/libpython2.6.so.1: symbolic link to `libpython2.6.so.1.0'
~> file /usr/lib/libpython
Hi,
I've got a seemingly simple question. However, I failed to find an answer up to
now.
In my FindXXX module, I search a library with help of the find_library command
on a 64-bit Linux. Now, I want to check, if the library is 32-bit (built with
-m32) or 64-bit.
How can I check this?
Thanks
On Tue, Jun 21, 2011 at 12:09 PM, Hugo Heden wrote:
> **
> Good day all,
>
> I am using ADD_TEST like this:
>
> ADD_TEST(
> nameOfMyTest
> ${CMAKE_CTEST_COMMAND}
> --build-and-test ${CMAKE_SOURCE_DIR} ${CMAKE_BINARY_DIR}
> --build-generator ${CMAKE_GENERATOR}
> --build-make
Good day all,
I am using ADD_TEST like this:
ADD_TEST(
nameOfMyTest
${CMAKE_CTEST_COMMAND}
--build-and-test ${CMAKE_SOURCE_DIR} ${CMAKE_BINARY_DIR}
--build-generator ${CMAKE_GENERATOR}
--build-makeprogram ${CMAKE_BUILD_TOOL}
--build-nocmake
--build-noclean
--bu
Am 21.06.2011 02:50, schrieb Tim Gallagher:
Hi,
I'm trying to set up automated testing of our code with CTest (we are using
CMake), but I'm running into some issues I can't figure out the correct way to
solve. Many of our tests require specific sets of options to be turned on/off
in the confi
Hi,
I'm trying to set up automated testing of our code with CTest (we are using
CMake), but I'm running into some issues I can't figure out the correct way to
solve. Many of our tests require specific sets of options to be turned on/off
in the configuration step.
How is this done? We've used
Hi,
Another add_test() question. I reuse the same test directory because
I run both Fortran and C executables on the same test and the input
files are so large that I don't want to replicate the entire test
hierarchy. The problem is that I need to remove files both before I
run the firs
On Thu, Dec 9, 2010 at 12:04 PM, Tyler Roscoe wrote:
> Ok I've added a link to this thread and the patch below to the bug:
> http://www.vtk.org/Bug/view.php?id=11561
>
> Without feedback from anyone, I will assume that I have done an awesome,
> production-ready job and will await the call for pat
Ok I've added a link to this thread and the patch below to the bug:
http://www.vtk.org/Bug/view.php?id=11561
Without feedback from anyone, I will assume that I have done an awesome,
production-ready job and will await the call for patches to add to CMake
2.8.4.
Thanks,
tyler
On Tue, Dec 07, 2010
In the process of attempting to fix this, I learned a lot of stuff about
how COST is handled that I've never encountered in the docs. Am I
missing something?
Here are some notes I made about the behavior of COST in CTest. If
others find them useful, I'd be happy to put them in the Wiki if someone
I've taken the liberty of adding this bug to the tracker:
http://www.cmake.org/Bug/view.php?id=11561
Can someone give me an idea of how involved this fix is? If it cannot be
fixed in short order, I'll be forced to hack around the change in COST's
behavior in my own scripts. Fixing the problem at
On Tue, Nov 30, 2010 at 01:29:37PM -0500, Zach Mullen wrote:
> Hm, yours was a use case we didn't really consider when we were making
> changes to cost behavior.
Clearly. :)
> The middle ground here would be to respect costs in the non-parallel
> case when they are expressed explicitly
This so
Hm, yours was a use case we didn't really consider when we were making
changes to cost behavior. The middle ground here would be to respect costs
in the non-parallel case when they are expressed explicitly, but not to
cost-order them automatically based on their previous run times.
-Zach
On Tue,
On Fri, Nov 26, 2010 at 10:38:44AM -0500, Zach Mullen wrote:
> I just realized why this isn't working -- it's actually not a regression.
Maybe we have different definitions of "regression". I see a feature
that used to do one thing but which now does something else.
Here is what the docs say abou
ing lines like this in my generated CTestTestfile.cmake:
>> >
>> >SET_TESTS_PROPERTIES(rs_exerciser_2dgrid PROPERTIES COST "-500"
>> FAIL_REGULAR_EXPRESSION "TP_EXERCISER_FAIL")
>> >
>> > and the FAIL_REGULAR_EXPRESSIO
OPERTIES(rs_exerciser_2dgrid PROPERTIES COST "-500"
> FAIL_REGULAR_EXPRESSION "TP_EXERCISER_FAIL")
> >
> > and the FAIL_REGULAR_EXPRESSION property seems to be working just fine.
> >
> >
> > I've included a small repro case below
; SET_TESTS_PROPERTIES(rs_exerciser_2dgrid PROPERTIES COST "-500"
> FAIL_REGULAR_EXPRESSION "TP_EXERCISER_FAIL")
>
> and the FAIL_REGULAR_EXPRESSION property seems to be working just fine.
>
>
> I've included a small repro case below. This looks like a
t;TP_EXERCISER_FAIL")
and the FAIL_REGULAR_EXPRESSION property seems to be working just fine.
I've included a small repro case below. This looks like a regression. Should I
open a bug?
Thanks,
tyler
[tyle...@tpb006:~/cmake-test-properties-test]$ cat CMakeLists.txt
cmake_minimum_required(VERSION 2.
test
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscr
Well it turns out the problem was in the execute_process script. I had the :
OUTPUT_FILE ${TEST_OUTPUT}
ERROR_FILE ${TEST_OUTPUT}
both going to one file - Windows couldn't handle that. Changing that allowed
the command to actually execute,
NOW, I have to deal with the CRLF issue i
As stated in my previous post, I have a script, named runTest.cmake, which
works on linux but fails on Windows with:
"The process cannot access the file because it is being used by another
process"
This script calls execute_process() with an executable to capture the output
for a comparison
I have a test script that works on linux but fails to work properly on Windows.
It runs a command, captures the standard out and compares it to a reference
file.
On linux everything works 99% of the time (issue with '=' or '--' in a
parameter argument - later question). On windows, the executio
If you use set_property instead, there's an APPEND mode to make this easier:
set_property(TEST test3 APPEND PROPERTY DEPENDS test2)
set_property(TEST test3 APPEND PROPERTY DEPENDS test1)
I think you can do it with set_tests_properties, too, like this:
SET_TESTS_PROPERTIES(test3 PROPERTIES DEPENDS
Hi,
I don't manage to have a test depend on multiple tests.
If I do :
SET_TESTS_PROPERTIES(test3 PROPERTIES DEPENDS test2)
SET_TESTS_PROPERTIES(test3 PROPERTIES DEPENDS test1)
test3 only depends on test1
and
SET_TESTS_PROPERTIES(test3 PROPERTIES DEPENDS test1 test2)
is not a valid syntax.
S
On Friday 12 March 2010, David Cole wrote:
> ctest -R "test1|test2" ?
>
> Using -R says "run only the tests that match this regex" -- it does not say
> "run the matching tests after running all the tests they depend on
> first"...
Well, OTOH if I do "make some_target" with cmake-generated makefile
ctest -R "test1|test2" ?
Using -R says "run only the tests that match this regex" -- it does not say
"run the matching tests after running all the tests they depend on first"...
On Fri, Mar 12, 2010 at 12:37 PM, Alexandre Gramfort <
alexandre.gramf...@inria.fr> wrote:
> Hi,
>
> here is a simple
Hi,
here is a simple CMakeList to illustrate my problem:
---
PROJECT(Test)
CMAKE_MINIMUM_REQUIRED(VERSION 2.8)
ENABLE_TESTING()
ADD_TEST(test1 ${CMAKE_COMMAND} -E touch test1.txt)
ADD_TEST(test2 ${CMAKE_COMMAND} -E touch test2.txt)
SET_TESTS_PROPERTIES(test2 PROPERTIES DEPENDS test1)
Matthew Leotta wrote:
>
> On Jan 26, 2009, at 3:04 PM, Brad King wrote:
>> add_test(run_xterm xterm)
>>
>> $ ctest -R run_xterm
>>
>> Then run gdb and the test inside the xterm to see if it fails. It could
>> be an environment difference.
>>
>> -Brad
>>
>
> It runs fine from within xterm when xt
On Jan 26, 2009, at 3:29 PM, Matthew Leotta wrote:
On Jan 26, 2009, at 3:04 PM, Brad King wrote:
Matthew Leotta wrote:
Brad,
Thanks, but I'm not sure if I completely understand your suggestion.
Let me clarify. If I run the test executable
./bvxm_test_all
I get no errors and no segfault.
On Jan 26, 2009, at 3:04 PM, Brad King wrote:
Matthew Leotta wrote:
Brad,
Thanks, but I'm not sure if I completely understand your suggestion.
Let me clarify. If I run the test executable
./bvxm_test_all
I get no errors and no segfault. I know how to debug this, but
there is
nothing t
Matthew Leotta wrote:
> Brad,
>
> Thanks, but I'm not sure if I completely understand your suggestion.
> Let me clarify. If I run the test executable
>
> ./bvxm_test_all
>
> I get no errors and no segfault. I know how to debug this, but there is
> nothing to debug. If in the same directory
Brad,
Thanks, but I'm not sure if I completely understand your
suggestion. Let me clarify. If I run the test executable
./bvxm_test_all
I get no errors and no segfault. I know how to debug this, but there
is nothing to debug. If in the same directory I run
ctest
then the test will
Matthew Leotta wrote:
> I've come across a test on the VXL dashboard that seems to segfault only
> on some test machines.
>
> http://www.cdash.org/CDash/testSummary.php?project=12&name=bvxm_test_apm_processors&date=2009-01-26
>
>
> One of the failing machines is mine (Mac_OS_X-10.5.6_unix_make).
I've come across a test on the VXL dashboard that seems to segfault
only on some test machines.
http://www.cdash.org/CDash/testSummary.php?project=12&name=bvxm_test_apm_processors&date=2009-01-26
One of the failing machines is mine (Mac_OS_X-10.5.6_unix_make). When
I run the same test execu
Hi i am new, live from spain (bad english)
i am testing if we can read me
Bye :P
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Hi!
Does CTest have any support for acyclic unit/regression/functionality
test dependencies? i.e. can you enforce that certain tests pass before
continuing with the others? Also, is there any support for
automatically figuring out what these dependencies are based on source
code #includes etc.?
Che
Sorry for the noise.. Just trying to troubleshoot something with
gmail...
--
Mike Jackson
imikejackson & gmail * com
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
On Saturday 09 February 2008, James Bigler wrote:
> Is there an expression similar to the one for variables to determine if a
> macro is defined?
>
> MACRO(TEST)
>MESSAGE("TEST is defined")
> ENDMACRO(TEST)
>
> IF(DEFINED TEST)
>TEST()
> ELSE(DEFINED TEST)
>MESSAGE("TEST is not defined"
James Bigler wrote:
Is there an expression similar to the one for variables to determine if a macro
is defined?
MACRO(TEST)
MESSAGE("TEST is defined")
ENDMACRO(TEST)
IF(DEFINED TEST)
TEST()
ELSE(DEFINED TEST)
MESSAGE("TEST is not defined")
ENDIF(DEFINED TEST)
I don't think there is
Is there an expression similar to the one for variables to determine if a macro
is defined?
MACRO(TEST)
MESSAGE("TEST is defined")
ENDMACRO(TEST)
IF(DEFINED TEST)
TEST()
ELSE(DEFINED TEST)
MESSAGE("TEST is not defined")
ENDIF(DEFINED TEST)
James
__
On Tuesday 04 December 2007, Mike Jackson wrote:
> I need to test for icc/icpc (The intel compiler). What would be the
> best way to do that?
With cmake cvs you can check the compiler id (CMAKE_C_COMPILER_ID or something
similar), with cmake 2.4.x you have to check the filename of the compiler I
but I want to specifically look for the intel compiler. I guess I
could just exec icc and see what comes back. Checking for $CC=icc
might be useful, but mine is set to /opt/intel/cc/10.0.023/bin/icc..
Any suggestions would be good.
I use this:
SET(MANTA_COMPILER_NAME_REGEXPR "icc.*$")
IF(
I need to test for icc/icpc (The intel compiler). What would be the
best way to do that?
I could do:
IF (NOT CMAKE_COMPILER_IS_GNUCC)
but I want to specifically look for the intel compiler. I guess I
could just exec icc and see what comes back. Checking for $CC=icc
might be useful, but min
Please ignore this message.
--
Cheers,
Chen.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Matthew Woehlke wrote:
[It] turns out g++ is broken, at least in that binaries
it produces all have this problem. Which means I seem to have found a
"bug"; tests that involve compiling C++ programs either a: ignore that I
was using CC=cc CXX=CC to build cmake, or b: fail to notice that g++
pro
Matthew Woehlke wrote:
Bill Hoffman wrote:
Matthew Woehlke wrote:
A while back I "successfully"* built CMake on an x86/Solaris 10 box.
Now, trying to build on a different box, I am getting a 51% failure
rate in the test suite. Huh?!
(* the test suite has an odd problem with GNU make 3.81, ot
Bill Hoffman wrote:
Matthew Woehlke wrote:
A while back I "successfully"* built CMake on an x86/Solaris 10 box.
Now, trying to build on a different box, I am getting a 51% failure
rate in the test suite. Huh?!
(* the test suite has an odd problem with GNU make 3.81, otherwise it
was clean)
Matthew Woehlke wrote:
A while back I "successfully"* built CMake on an x86/Solaris 10 box.
Now, trying to build on a different box, I am getting a 51% failure
rate in the test suite. Huh?!
(* the test suite has an odd problem with GNU make 3.81, otherwise it
was clean)
I also can't seem to
A while back I "successfully"* built CMake on an x86/Solaris 10 box.
Now, trying to build on a different box, I am getting a 51% failure rate
in the test suite. Huh?!
(* the test suite has an odd problem with GNU make 3.81, otherwise it
was clean)
I also can't seem to find any output from th
On Monday 19 February 2007 16:08:08 Ken Martin wrote:
> We have a test for CREATE_TEST_SOURCELIST in CMake/Tests/TestDriver and it
> does not use a full path to the tests and it is passing on the dashboard.
> Perhaps you specified the path to the test source files as a full absolute
> path?
Thanks
12065
518 371 3971
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Pascal
Fleury
Sent: Sunday, February 18, 2007 6:18 PM
To: cmake@cmake.org
Subject: [CMake] Test sources
Hi CMakers,
I am trying to use the CREATE_TEST_SOURCELIST approach to test some
Hi CMakers,
I am trying to use the CREATE_TEST_SOURCELIST approach to test some existing
CppUnit tests. My plan was to have the functions that CTest expects ( the
foo(int,char**) for test in file 'foo.cpp' ) be generated, each of them
calling the suite from the CppUnit (basically testing a comp
Michael Biebl wrote:
The template files for CheckIncludeFile are not ansi conform, this
means running with "CFLAGS=-Werror -Wstrict-prototypes" produces
failing tests.
The template file CheckIncludeFile.c.in and the one for cxx should
correctly read
#include <${CHECK_INCLUDE_FILE_VAR}>
int mai
The template files for CheckIncludeFile are not ansi conform, this
means running with "CFLAGS=-Werror -Wstrict-prototypes" produces
failing tests.
The template file CheckIncludeFile.c.in and the one for cxx should
correctly read
#include <${CHECK_INCLUDE_FILE_VAR}>
int main(int argc, char *argv
87 matches
Mail list logo
