[Re-sending in text-form]
Hi,
I'm failing to be able to use "run-only-in-release" tests when running under
linux (Debian). Below is a short reproduction.
CmakeLists.txt
=
cmake_minimum_required(VERSION 3.0)
enable_testing()
add_test(NAME list-stuff
CONFIGURATIONS Release
COMM
Hi,
I'm failing to be able to use "run-only-in-release" tests when running under
linux (Debian).
Below is a short reproduction.
CmakeLists.txt
=
cmake_minimum_required(VERSION 3.0)
=
CMAKE_BUILD_TYPE=Release. Correct? Doesn't work for me:
Run Script
==
st
On Sat, Nov 26, 2011 at 10:46:10AM -0500, John Drescher wrote:
> On Fri, Nov 25, 2011 at 10:16 PM, Steve M. Robbins wrote:
> > Hi,
> >
> > To build VTK on our windows build server, I wrote a small batch script
> > that invokes "cmake --build".
> >
> &
Hi,
To build VTK on our windows build server, I wrote a small batch script
that invokes "cmake --build".
My developer machine is multicore; is there a way to get "cmake --build"
to run multiple jobs?
Thanks,
-Steve
signature.asc
Description: Digital signature
--
Powered by www.kitware.com
V
Hi,
The FindwxWidget.cmake module in 2.8 is breaking the build of
MRIConvert [1] because it strips "-D" from the output of "wx-config
--cxxflags".
Is this not a bug?
This question was asked here last October [2] but not answered.
Thanks,
-Steve
[1] http://lcni.uoregon.edu/~jolinda/MRIConvert
Hi again,
I found the answer to my problem in the CMake FAQ. Hurray!
On Wed, Aug 29, 2007 at 09:19:51AM -0500, Steve M. Robbins wrote:
> Reluctantly, I gave up and went back to ADD_CUSTOM_TARGET. The
> following gives me exactly what I want:
[...]
The clue I need
Hi,
I'd appreciate some advice for writing test cases using Boost.Test
under windows / msvc.
My first trial was, following the advice of the Boost.Test authors
(http://www.boost.org/libs/test/doc/usage/msvc_net.html), to create a
custom build step in visual studio. This produces output that visu
Hi,
Anyone out there with advice for writing test cases with Boost.Test
under windows / msvc ?
My first trial was, following the advice of the Boost.Test authors
(http://www.boost.org/libs/test/doc/usage/msvc_net.html), to create a
custom build step in visual studio. This produces output that vi
