Is there a way to build multiple build types at one go?
I would like to be able to build Debug and Release like
nmake debug; nmake install
nmake release; nmake install
assuming that both versions install to different directories.
Thanks!
-Marcin
___
Von: Marcin Gil [EMAIL PROTECTED]
Is there a way to build multiple build types at one go?
I would like to be able to build Debug and Release like
nmake debug; nmake install
nmake release; nmake install
assuming that both versions install to different directories.
You could setup two
It works in the VTK build tree...
What version of cmake/ctest?
What style dashboard scripts are you using?
How does your CONFIGURE_FILE for CTestCustom compare to the one found in
VTK's top level CMakeLists.txt?
Warnings are only suppressed when reported as part of a ctest driven
dashboard run.
Hello all,
recently I have encountered a unexpected behaviour of ADD_DEPENDENCIES. My
goal is to have a set of targets that are not built with the ALL-target.
They should be built using an empty helper-target. The helper-target is an
empty custom target in a CMakeLists.txt in some root-directory:
Hi!
My source directory looks like this:
ProjectName/
/00 Bin
/10 Build
/Debug
/Release
/50 Common
/SBF
I have CMakeLists.txt
ProjectName/
CMakeLists.txt:
PROJECT(ProjectName)
ADD_SUBDIRECTORY(50 Common)
/50 Common
CMakeLists.txt:
ADD_SUBDIRECTORY(SBF)
/SBF
Von: Marcin Gil [EMAIL PROTECTED]
On 1/4/07, Alexander Neundorf [EMAIL PROTECTED] wrote:
You could setup two out-of-source buildtrees and compile each with a
different buildtype. Is this good enough ?
Hmm.. never thought of this. So my layout would be
build/
/debug
GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
?xml version=1.0 encoding=UTF-8?
Site BuildName=Linux-c++ BuildStamp=20070104-1427-Experimental Name=pc-neundorf1 Generator=ctest2.4-patch 4
Configure
StartDateTimeJan 04 15
Dnia czwartek, 4 stycznia 2007 16:11, Alexander Neundorf napisał:
You could setup two out-of-source buildtrees and compile each with a
different buildtype. Is this good enough ?
Hmm.. never thought of this. So my layout would be
build/
/debug
/release
go in both
[EMAIL PROTECTED] wrote:
I'm porting over my build system to use cmake to build my program
under nmake (VS2005).
If I start the build manually, everything works fine. Doing the same
things as a cron job
however, does not.
build command: cmd /C vcvars32.bat cmake -G NMake Makefiles .
nmake
hi,
I recently installed the lapack library on my linux box and would like
to configure cmake to use it. I steal the FindLapack.cmake file from
http://www.mip.informatik.uni-kiel.de/~jw/cmake/CMakeModules/FindLAPACK.cmake
(btw, I also use the FindGSL.cmake from there and it works great)
and put
Von: Marcin Gil [EMAIL PROTECTED]
Dnia czwartek, 4 stycznia 2007 16:11, Alexander Neundorf napisał:
...
Yes.
It would be cool if you could add a note about this in the CMake Wiki:
http://www.cmake.org/Wiki/CMake :-)
Done here
Yup, I'l check in a fix for it. add_executable does it correctly.
Thanks
Ken
Ken Martin PhD
Kitware Inc.
28 Corporate Drive
Clifton Park NY 12065
518 371 3971
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
wedekind
Sent: Thursday, January 04, 2007
On 1/4/07, Bill Hoffman [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
hi,
I recently installed the lapack library on my linux box and would like
to configure cmake to use it. I steal the FindLapack.cmake file from
Hi,
I don't have a Mac available, so I can't test myself.
In June the following change to FindQt4.cmake was committed:
http://www.cmake.org/cgi-bin/viewcvs.cgi/Modules/FindQt4.cmake?rev=1.59root=CMakeview=log
There is this big chunk of code for frameworks removed inside
IF (QT_USE_FRAMEWORKS)
Hi,
Von: [EMAIL PROTECTED]
...
However, when I make the program, I got the following message seems
there is a link problem:
$ make
Scanning dependencies of target test
[100%] Building C object CMakeFiles/test.dir/testunsymm.o
Linking C executable test
/usr/bin/ld: cannot find -llapack
Am Donnerstag, den 04.01.2007, 16:37 -0500 schrieb [EMAIL PROTECTED]:
hi, Bill
I made some corrections and with manually set up the locations in
cmake, ccmake . is now doing fine. My CMakeLists.txt is
PROJECT(ta)
FIND_PACKAGE(GSL)
INCLUDE_DIRECTORIES(${GSL_INCLUDE_DIR})
Hi Maik,
Thanks for the Christmas present ;-) I tried your code with gcc.
The following issues/suggestions came to my mind:
1) It seems to me (and it worked for me) that you don't need to
have CMAKE_CURRENT_BINARY_DIR in the include path if you change
the target cflags determination into
Hi. I have some code that creates out-of-source builds, by defining:
EXECUTABLE_OUTPUT_PATH
LIBRARY_OUTPUT_PATH
CMAKE_LIBRARY_PATH
CMAKE_BUILD_TYPE
This is working okay, but my problem is that cmake's build system is
still a tad simplistic for my taste. Even when I set all those
variables,
18 matches
Mail list logo