Arnaud,
I use valgrind with options using something like this:
set( CTEST_MEMORYCHECK_COMMAND valgrind )
set( CTEST_MEMORYCHECK_COMMAND_OPTIONS --tool=callgrind -v )
Let us know if that works.
-kt
-Original Message-
From: cmake-boun...@cmake.org
Jack,
1. As Michael mentioned - ensure that you are linking to the BLAS
library:
find_package(BLAS REQUIRED)
add_executable( foo ${sources} )
target_link_library( foo ${BLAS_LIBRARIES} )
2. FYI - For the Makefile Generator, the object files are usually stored
in a
Dave,
I usually run 'ctest -j4' because it is easier to type than 'make test
ARGS=j4'.
I think that 'make test ARGS=j4' will simply call ctest with '-j4' so the
commands should be equivalent.
-kt
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On
bit of sarcasm accompanied by a wry smile...)
What version of ctest?
Is this a project that is publicly available, so that I can try to reproduce
it here and help these innocent coders...?
Thanks,
David
On Wed, Apr 20, 2011 at 6:35 PM, Kelly Thompson k...@lanl.gov wrote:
Fellow CMake users
Fellow CMake users:
I'm having a problem with one of my projects when I run 'ctest -jN'. The
problem is that after 70-90 tests, ctest decides to submit all of the
remaining tests at once (~200 tests worth). For example (actual test names
replaced to protect the innocent :-)
% ctest -j16
Test
Allen,
We experienced something similar. Unfortunately, I never diagnosed the
actual problem because I assumed that my ctest scripts were simply
out-of-date and I replaced them. In particular, the ctest scripts that
produced broken memcheck output were trying to use the 'ctest
Marcel,
We use a 'bootstrap' CMakeCache.txt file that has README-like full
documentation for each user settable variable. This way a new developer can
copy the bootstrap CMakeCache.txt file to his/her build directory and edit
the file variable-by-variable before running cmake.
Something like:
Thanks Mike!
That work like a charm. I'm not sure why I overlooked that portion of the
user manual. Thanks for being patient.
-kt
-Original Message-
From: Michael Wild [mailto:them...@gmail.com]
Sent: Tuesday, July 20, 2010 2:00 PM
To: Kelly Thompson
Cc: cmake@cmake.org
Subject
Hi Arjen,
This may be totally the wrong direction, but we have seen similar errors
that appear to be caused by resident programs that crawl the local
filesystem. Desktop search engines (Microsoft or Google) or anti-virus
software may try to open your build files (including temporary files)
Hi,
I am having trouble with add_test and the MSVC macro $(Configuration) when I
generate project files for Visual Studio. I am hoping someone on this list
can provide a solution.
Scenario: (This is an outline of what I want to do.)
1. Ceating a unit test via
This can be done using a Fortran compile option. For gfortran, add the
option -Mdir to CMAKE_Fortran_FLAGS.
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf
Of
Jed Brown
Sent: Monday, May 31, 2010 5:41 AM
To: cmake@cmake.org
Subject:
On Tuesday, June 01, 2010 at 11:48 AM, Brad King wrote:
You can delete the object file the provides the module.
Perhaps that scenario where
module files are deleted independent of the object/libraries is
artificial, but it's not really correct for the build to break if they
are
John,
I'm not aware of any 'out of the box' way to install .mod files. Here's
what I did for my project:
First, I wrote a set of macros that would determine the how FC names module
files (evidently there is no standard naming scheme) by using the
try_compile() macro.Next, I created a
13 matches
Mail list logo
