Hi, I am going to enable coverage test in my project,
I have enabled the following compile options:
---
CXXFLAGS=-g -O0 -Wall -Wshadow \
-Wunused-function -Wunused -Wno-system-headers \
How are you running ctest to try to get the coverage reported?
With -D NightlyCoverage?
With a -S script?
What version of ctest?
On Wed, Aug 25, 2010 at 3:31 AM, emeplease emeple...@gmail.com wrote:
Hi, I am going to enable coverage test in my project,
I have enabled the following
Hi all.
I need to use different link paths for Debug and Release builds of my
software. I'm building with the Visual Studio Generator (2005, 2008,
etc). I had put this in my CMakeLists.txt, but as it turns out, this
doesn't do what I need (likely because of the single pass to generate
the
Hello,
I am using Cmake to run some tests after building my executable; my
tests are .sh scripts. I would like them to be Python scripts instead.
I wrote the following test script:
print success
exit(0)
While the correspondent shell script will work, the Python equivalent
exits complaining
Hello,
I am using Cmake to run some tests after building my executable; my
tests are .sh scripts. I would like them to be Python scripts instead.
I wrote the following test script:
print success
exit(0)
While the correspondent shell script will work, the Python equivalent
exits
Show us your add_test call.
If it's a python script, execute the python interpreter and pass the script
as an arg:
add_test(${PYTHON_EXECUTABLE} /full/path/to/script.py)
On Wed, Aug 25, 2010 at 10:39 AM, Mattia Tomasoni
mattia.tomasoni.8...@student.uu.se wrote:
Hello,
I am using Cmake to
Zitat von aaron.mead...@thomsonreuters.com:
I need to use different link paths for Debug and Release builds of my
software. I'm building with the Visual Studio Generator (2005, 2008,
etc). I had put this in my CMakeLists.txt, but as it turns out, this
doesn't do what I need (likely because of
2010/8/25 aaron.mead...@thomsonreuters.com:
Hi all.
I need to use different link paths for Debug and Release builds of my
software. I’m building with the Visual Studio Generator (2005, 2008, etc).
I had put this in my CMakeLists.txt, but as it turns out, this doesn’t do
what I need
Hi, David , Thank you for your quick reply.
I am so sorry to have missed this important detail : cmake-2.6.4-7.el5.
I am trying to get the coverage report by running -S script, the
script basically
works by ctest -D NighlyBuild, ctest -D NightlyCoverage ...
I have noticed that the
On Wed, Aug 25, 2010 at 11:11 AM, Eric Noulard eric.noul...@gmail.comwrote:
2010/8/25 David Cole david.c...@kitware.com:
Show us your add_test call.
If it's a python script, execute the python interpreter and pass the
script
as an arg:
add_test(${PYTHON_EXECUTABLE}
Hi
find_package(PythonInterp REQUIRED)
add_test(NAME some_test
COMMAND ${PYTHON_EXECUTABLE}
${CMAKE_CURRENT_BINARY_DIR}/run_test.py
some_test)
or similar should do the trick.
Michael
On 25.08.2010, at 16:38, Mattia Tomasoni mattia.tomasoni.8...@student.uu.se
wrote:
Hello,
I am
A while ago I started looking at using CMake to build OCaml projects. As part
of that I put together some useful (but maybe not very beautiful) macros.
They are available on github[1].
I've come to the conclusion that while CMake is a rather good build tool, it
isn't very well designed to add
2010/8/25 Magnus Therning mag...@therning.org:
A while ago I started looking at using CMake to build OCaml projects. As part
of that I put together some useful (but maybe not very beautiful) macros.
They are available on github[1].
I've come to the conclusion that while CMake is a rather
2010/8/25 aaron.mead...@thomsonreuters.com:
Ok, I'll give that a shot. I wonder if I could iterate the list of targets
and make the target_link_libraries() calls on them in a loop.
You can do that.
However I am not aware of a way to get the list of targets
from within a CMakeLists.txt with
Ok, I'll give that a shot. I wonder if I could iterate the list of targets and
make the target_link_libraries() calls on them in a loop.
Aaron C. Meadows
-Original Message-
From: Eric Noulard [mailto:eric.noul...@gmail.com]
Sent: Wednesday, August 25, 2010 9:59 AM
To: Meadows, Aaron
Hey,
I was trying to use the SYSTEM option in the include_directories command
, however it does not seem to work on the MACOSX platform. So i wrote a
little fix which basically replaces all the -I${foldername} with
-isystem ${foldername}. However these commands need to be executed after
my
On 2010-08-25 16:32+0100 Magnus Therning wrote:
I've come to the conclusion that while CMake is a rather good build tool, it
isn't very well designed to add full support for slightly esoteric languages
and tool chains like OCaml.
I generally agree with that conclusion concerning CMake
On 25. Aug, 2010, at 18:57 , Johny wrote:
Hey,
I was trying to use the SYSTEM option in the include_directories command ,
however it does not seem to work on the MACOSX platform. So i wrote a little
fix which basically replaces all the -I${foldername} with -isystem
${foldername}.
On 2010-08-25 17:50+0200 Eric Noulard wrote:
2010/8/25 Magnus Therning mag...@therning.org:
A while ago I started looking at using CMake to build OCaml projects. As part
of that I put together some useful (but maybe not very beautiful) macros.
They are available on github[1].
I've come to
On Wed, Aug 25, 2010 at 3:01 PM, Michael Wild them...@gmail.com wrote:
On 25. Aug, 2010, at 18:57 , Johny wrote:
Hey,
I was trying to use the SYSTEM option in the include_directories command ,
however it does not seem to work on the MACOSX platform. So i wrote a little
fix which
2010/8/25 Alan W. Irwin ir...@beluga.phys.uvic.ca:
On 2010-08-25 17:50+0200 Eric Noulard wrote:
2010/8/25 Magnus Therning mag...@therning.org:
A while ago I started looking at using CMake to build OCaml projects. As
part
of that I put together some useful (but maybe not very beautiful)
I was had trouble getting FindBoost.cmake to work correctly and I found that
there was a variable I had to adjust in the FindBoost.cmake file:
set(_Boost_KNOWN_VERSIONS ${Boost_ADDITIONAL_VERSIONS}
1.41.0 1.41 1.40.0 1.40 1.39.0 1.39 1.38.0 1.38 1.37.0
1.37
1.36.1 1.36.0 1.36
I am using Google Tests to create unit tests for our software. We are
using CMake (version 4.6-patch 2) for building the unit tests
executable. Since the list of unit tests is expected to grow to
thousands of tests, I am looking for a way to automate creating a file
(say testlist) on the fly
Someone has included 1.44 in the latest FindBoost.cmake in git.
On Wed, Aug 25, 2010 at 3:35 PM, Dixon, Shane shane.di...@atmel.com wrote:
I was had trouble getting FindBoost.cmake to work correctly and I found
that there was a variable I had to adjust in the FindBoost.cmake file:
I'm starting to get deep into CMake, and I have a few questions as I
try to convert the socket++ library such that it can be compiled by
CMake on Windows.
1) The default install directory on Windows is C:\Program Files, or
C:\Program Files (x86) on 64 bit. This default will not work on
Windows 7
Hi Eric:
On 2010-08-25 22:20+0200 Eric Noulard wrote:
[...]My ideas was that some languages:
- OCaml (ocamlbuild)
- ADA (gnatmake)
- may Java too (ant/maven)
have already very efficient build tool with some history of usage too.
I don't know many Java developers who speaks
On Wed, Aug 25, 2010 at 3:17 PM, Neelima Mehdiratta nmehdira...@decarta.com
wrote:
ADD_CUSTOM_COMMAND(TARGET ${BIN_NAME}
POST_BUILD
WORKING_DIRECTORY ${SRC_DIR}
COMMAND bash ./addtestscrpt
COMMAND ${CMAKE_COMMAND} ${SRC_DIR}/DDSCommonTests/CMakeLists.txt
)
I'm not
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, hooks has been updated
via 0c6925a7fc869b32ceb07d043de79f3b4247d0ad (commit)
from
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 095fb5bf2d6184faa6997ac70991a6f13ad5eed8 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 5cb07af0601286e1ab18a2208cb7ae07d2aaa411 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 7485a2c94938a83187ea938ac6ebb690f7990abf (commit)
via
31 matches
Mail list logo
