Hello,
I am still experimenting and learning how to setup CTest/CDash support
for our projects.
We have the following directory structure for our projects:
Foo/
cmake
CMakeLists.txt
CTestConfig.cmake
include
Foo.h
src
Foo.cpp
FooTest.cpp
Running CM
Johannes,
Is there any compelling reason to place the cmake "control files" in a
directory under the root?
Foo/
CMakeLists.txt
CTestConfig.cmake
include
Foo.h
src
Foo.cpp
FooTest.cpp
is a more conventional structure
On Nov 10, 2009, at 2:43 AM, Johannes Stallka
Richard,
Richard Wackerbarth schrieb:
> Johannes,
>
> Is there any compelling reason to place the cmake "control files" in a
> directory under the root?
>
> Foo/
>CMakeLists.txt
>CTestConfig.cmake
>include
> Foo.h
>src
> Foo.cpp
> FooTest.cpp
>
> is a more convent
I need to run a script on a C++ executable after it's linked that will
modify the exe, before it's really done building. Is there a way to
hook into the "add_executable" handling to do this?
Thanks,
Kevin
___
Powered by www.kitware.com
Visit other
On Tue, Nov 10, 2009 at 08:36:10AM -0600, Kevin Burge wrote:
> I need to run a script on a C++ executable after it's linked that will
> modify the exe, before it's really done building. Is there a way to
> hook into the "add_executable" handling to do this?
Have you looked at add_custom_command
CMake 2.8.0 RC 6 is now ready for people to try. This is getting very
close to the final 2.8.0. I think this is the last one. Please let me
know if you find any serious regressions. I hope to release 2.8.0 final
this week. Thanks.
You can find the source and binaries here: http://www.cmake
Whoops, forgot to follow up on this.
On Tue, Oct 20, 2009 at 03:27:50PM -0400, David Cole wrote:
> One easy way to hack around this problem would be to use add_custom_command
> to invoke the rc.exe directly...
>
> Not sure if you could just include a *.res file (output from rc) as a source
> in a
2009/11/9 Ingolf Steinbach :
> It is still in there when using cmake-2.8.0-rc2-Linux-i386.
Sorry, I only had those rc2 pre-compiled binaries. I have now tried
again with rc6 and can confirm that -fPIC is no longer inserted in the
command line used for linking.
Kind regards
Ingolf
Hello,
When running this script http://dpaste.com/118717/ via ctest -VV -S,
it fails with
{{{
Cannot instantiate test handler ctest_build
CMake Error at ctest_core.cmake:46 (ctest_build):
ctest_build CTEST_BUILD_COMMAND or CTEST_CMAKE_GENERATOR not specified.
Please specify the CTEST_CMAKE_GEN
That worked! Thanks.
Tyler Roscoe wrote:
On Tue, Nov 10, 2009 at 08:36:10AM -0600, Kevin Burge wrote:
I need to run a script on a C++ executable after it's linked that will
modify the exe, before it's really done building. Is there a way to
hook into the "add_executable" handling to do thi
I'm trying to figure out in what scenarios one might use import/export verses
using the new ExternalProject_add. I'm having a hard time understanding what
the differences are. I have a project that builds in simulation mode (using
microsoft cl compiler) and once testing is done, it's cross-com
I have many built targets. When I do "nmake install" it takes a long
time between each "Built target..." check (extremely long, compared to
using make on a Unix box). Is there any way to speed this up? It's
particularly slow on built C++ targets. It can take between 2-5 seconds
before it mo
Hi All,
This was asked a while ago at
http://www.cmake.org/pipermail/cmake/2009-January/026318.html, but it
doesn't look like there was a response to that question.
I have the same problem:
on 64 bit AIX, ar must be invoked with a "-X 64" flag. Is there a way
to tell CMake to do this?
Th
James C. Sutherland wrote:
The library I am building pulls in several other libraries (MPI, BLAS,
Boost, etc). I would like any down-stream apps that use my library to
automatically be able to include any appropriate header files and link
to appropriate third-party libraries that were included
Kevin Burge wrote:
> I have many built targets. When I do "nmake install"
FYI, you can skip the up-to-date check before install by using
nmake install\fast
> it takes a long
> time between each "Built target..." check (extremely long, compared to
> using make on a Unix box). Is there any way
Dear CMakers,
Sorry for disturbing. Since nobody gave the answer, I just rephrased the
title of my question.
I am a beginner of CMake. My problem is that in MSVC, I have two projects:
one is executable project A, and the other is library project B. A depends
on B and A has to link B. I want A
Will Dicharry wrote:
> Hi All,
>
> This was asked a while ago at
> http://www.cmake.org/pipermail/cmake/2009-January/026318.html, but it
> doesn't look like there was a response to that question.
>
> I have the same problem:
>
> on 64 bit AIX, ar must be invoked with a "-X 64" flag. Is there a
I guess something in this chain
gcc->ctest->cdash
goes wrong. See the following example:
While this is what gcc outputs ( where LC_MESSAGES=C):
{{{
warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘size_t’
}}}
ctest makes this of it:
{{{
warning: format
<-30><-128><-104>%d<-3
Ups, missing details:
- cmake-2.6.4
- cdash-1.4.2
___
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.cma
I have a group of static archive libraries (.a libs) on Linux and because of
the way the linker does symbol resolution I need to use the
-Wl,--start-group and -Wl,--end-group linker options to group these
libraries. These linker options tell the linker to continue searching the
libraries for symb
hm, looks like LC_MESSAGES=C isn't enough, all compiler output has to be ascii.
LANG=C works.
Knowing this, I like to point out that on this site
http://www.cmake.org/Wiki/CMake_Scripting_Of_CTest
this statement
SET( $ENV{LC_MESSAGES}"en_EN" )
beside from it having to be
SET( ENV{LC_MESS
Never mind, I figured out how to do it...
You can use target_link_libraries() (because target_link_libraries also
accepts linker options) to do this kind of thing:
target_link_libraries(FOO -Wl,--start-group A B C -Wl,--end-group)
On Tue, Nov 10, 2009 at 12:30 PM, Steven Wilson <
steven.wesley
Brad King wrote:
Will Dicharry wrote:
Hi All,
This was asked a while ago at
http://www.cmake.org/pipermail/cmake/2009-January/026318.html, but it
doesn't look like there was a response to that question.
I have the same problem:
on 64 bit AIX, ar must be invoked with a "-X 64" flag. Is there
I’d like to force an update of the doxygen-generated documentation before I
create a package. It’d be nice if I could do something like:
add_dependencies(package doc)
where doc is a target that forces doxygen to run. However, this doesn’t work,
because the package target isn’t defined.
Will Dicharry wrote:
Brad King wrote:
Will Dicharry wrote:
Hi All,
This was asked a while ago at
http://www.cmake.org/pipermail/cmake/2009-January/026318.html, but it
doesn't look like there was a response to that question.
I have the same problem:
on 64 bit AIX, ar must be invoked with a "-
I’d like to force an update of the doxygen-generated documentation before I
create a package. It’d be nice if I could do something like:
add_dependencies(package doc)
where doc is a target that forces doxygen to run. However, this doesn’t work,
because the package target isn’t defined.
Brad, thanks for the feedback. See comments below.
On Nov 10, 2009, at 11:30 AM, Brad King wrote:
> James C. Sutherland wrote:
>> The library I am building pulls in several other libraries (MPI, BLAS,
>> Boost, etc). I would like any down-stream apps that use my library to
>> automatically be
On Tue, Nov 10, 2009 at 01:54:06PM -0600, Mark Moll wrote:
> add_dependencies(package doc)
>
> where doc is a target that forces doxygen to run. However, this
> doesn’t work, because the package target isn’t defined. How do I get
> around this?
You can't add dependencies to the "special" CM
Dear all,
For the compilation of my project, I want to provide a static or dynamic
linked final executable (e.g.: linking preferentially with .a or .so
libraries on Linux). For this, I set up a cache variable which enables to
modify CMAKE_FIND_LIBRARY_SUFFIXES (".a;.so" or ".so;.a"). By the way
On Tue, Nov 10, 2009 at 10:43:49AM -0800, Meng Zhang wrote:
> target_link_libraries(A debug Debug/B)
> target_link_libraries(A optimized Release/B)
>
> Nevertheless, obviously, since optimized means all the other three
> configurations except "Debug", project A won't find library B if I directly
On 2009-11-10 10:28-0500 Bill Hoffman wrote:
CMake 2.8.0 RC 6 is now ready for people to try. This is getting very
close to the final 2.8.0. I think this is the last one. Please let me know
if you find any serious regressions. I hope to release 2.8.0 final this
week. Thanks.
I tested RC
I've been trying to build the INSTALL project as part of the solution from
the commandline. For example, after running:
cmake -G "Visual Studio 9 2008" ..
I've tried:
msbuild /t:INSTALL /p:Configuration=Release solution.sln
But this builds ALL_BUILD and then tells me tells me:
The project "IN
Aaron,
Visual Studios should just be a driver for "nmake", so you could use:
cmake -G "NMake Makefiles" ..
and then use:
nmake install
The catch is that you have to run all that from the Visual Studio Command
Prompt so it knows where to find "nmake", "cl" and "link".
--
Shane Dixon
L
-- Forwarded message --
From: John Drescher
Date: Tue, Nov 10, 2009 at 5:22 PM
Subject: Re: [CMake] How to build INSTALL project from the command line?
To: aaron_wri...@selinc.com
On Tue, Nov 10, 2009 at 5:09 PM, wrote:
>
> I've been trying to build the INSTALL project as part
That did the trick. I've never used nmake directly before.
-
Aaron Wright
Software Engineer - DCS Group
Schweitzer Engineering Laboratories, Inc.
Pullman, WA 99163
509-334-8087
"Dixon, Shane"
11/10/2009 02:17 PM
To
, "CMake"
cc
Subject
Hello,
How does one ensure that the appropriate scanner is run to obtain
implicit dependencies via IMPLICIT_DEPENDS? In the following example,
the 'drop' target depends on dummy.cc which has an implicit dependency
on blah.h, which means that 'drop' should be rebuilt after every change
to blah.h.
On 2009-11-10 17:34-0500 lists_r...@lavabit.com wrote:
Hello,
How does one ensure that the appropriate scanner is run to obtain
implicit dependencies via IMPLICIT_DEPENDS? In the following example,
the 'drop' target depends on dummy.cc which has an implicit dependency
on blah.h, which means tha
Just to bring this to closure, I ended up creating a special directory
just to separate the static library target from the dynamic library
target. Both targets use the same sources, so there's some undesirable
redundancy between the two CMakeLists.txt files, but at least I was able
to get diffe
38 matches
Mail list logo
