So we've got a fairly sizable amount of code described in the CMake
framework now, about 10 or so libraries, and 4 projects which consume
them. We're now hitting upon compilation time as an issue, as it takes
much longer than our previous framework did. I'm wondering what can be
done to speed it
* We're using an NMake build tree, is NMake particularly
slow? Do any of the other makes work more efficiently?
Be aware that nmake builds are much slower than using devenv, as nmake starts a
cl.exe process for every single file,
whereas devenv calls cl.exe with several source files.
I have a CMakeLists.txt like this:
PROJECT(foo)
SET(CMAKE_ALLOW_LOOSE_LOOP_CONSTRUCTS TRUE)
INCLUDE(CheckIncludeFile)
CHECK_INCLUDE_FILE(poll.h VAR1)
CHECK_INCLUDE_FILE(sys/event.h VAR2)
When I run `cmake .' it outputed like this:
-- Check for working C compiler: /usr/bin/gcc
-- Check for
-Original Message-
From: Torsten Martinsen [mailto:[EMAIL PROTECTED]
Sent: 11 December 2007 09:08
To: Josef Karthauser; CMake ML
Subject: RE: [CMake] Compilation speed with CMake/NMake combination,
making it faster?
* We're using an NMake build tree, is NMake particularly
The header of many CMake modules often looks like this (take
CheckIncludeFile as an example):
MACRO(CHECK_INCLUDE_FILE INCLUDE VARIABLE)
IF(${VARIABLE} MATCHES ^${VARIABLE}$)
... ...
The IF statement really puzzles me a lot. What is it used to do?
On Dec 10, 2007 8:58 PM, Alan W. Irwin [EMAIL PROTECTED] wrote:
On 2007-12-10 17:08+0100 Tristan Carel wrote:
On Dec 10, 2007 7:15 AM, Alan W. Irwin [EMAIL PROTECTED] wrote:
On 2007-12-10 05:33+0100 Christiaan Putter wrote:
Hi all,
I know swig support isn't all that great at the
I'm quite jaded about keeping CMakeLists.txt simple. As far as I'm
concerned, it should be as simple as the level of complication of your
build. If I want encapsulation, I write a macro. Otherwise I'll just
write straight CMake script, because I'd rather read CMake script than
the docs of 5
I'm quite jaded about keeping CMakeLists.txt simple. As far as I'm
concerned, it should be as simple as the level of complication of your
build. If I want encapsulation, I write a macro. Otherwise I'll just
write straight CMake script, because I'd rather read CMake script than
the docs of 5
Von: Josef Karthauser [EMAIL PROTECTED]
-Original Message-
From: Torsten Martinsen [mailto:[EMAIL PROTECTED]
Sent: 11 December 2007 09:08
To: Josef Karthauser; CMake ML
Subject: RE: [CMake] Compilation speed with CMake/NMake combination,
making it faster?
* We're
Quoting Clark J. Wang [EMAIL PROTECTED]:
The header of many CMake modules often looks like this (take
CheckIncludeFile as an example):
MACRO(CHECK_INCLUDE_FILE INCLUDE VARIABLE)
IF(${VARIABLE} MATCHES ^${VARIABLE}$)
... ...
The IF statement really puzzles me a lot. What is it used to do?
On Dec 11, 2007 6:49 PM, Pau Garcia i Quiles [EMAIL PROTECTED] wrote:
Quoting Clark J. Wang [EMAIL PROTECTED]:
The header of many CMake modules often looks like this (take
CheckIncludeFile as an example):
MACRO(CHECK_INCLUDE_FILE INCLUDE VARIABLE)
IF(${VARIABLE} MATCHES
Christian Ehrlicher wrote:
* We're using an NMake build tree, is NMake particularly
slow? Do any of the other makes work more efficiently?
Be aware that nmake builds are much slower than using devenv, as nmake
starts a cl.exe process for every single file,
whereas devenv calls
Jian Wang wrote:
Why is IF(${VARIABLE} MATCHES ^${VARIABLE}$) used instead of IF(
${VARIABLE} STREQUAL ${VARIABLE} ) (which would always return true)?
I'm not sure of use case but I'd say it's checking for special
characters in VARIABLE.
If it's checking for special characters
On Dec 10, 2007, at 5:33 PM, Gonzalo Garramuño wrote:
I use my own variable -DCMAKE_BUILD_ARCH=32 to determine whether I
am compiling 32-bits on a 64-bits machine.
The problem is that cmake now goes to check compiler and it runs
Platform/UnixPaths.cmake without passing any of my variables
Bryan O'Sullivan wrote:
I have two sibling directories. In one of them, a binary is built, and
in the other, that binary is packaged up using a custom command. Is
there a way in the DEPENDS clause to express this dependency?
There are two levels of dependencies: file and target. File-level
The quotes may be confusing...
Try this exactly, with the quotes surrounding the whole thing, or without
the quotes: -DCMAKE_BUILD_TYPE:STRING=Debug
I think you are telling it to set the build type to Debug (including the
quotes) but for it to work, it needs to be exactly Debug without any
Bill Hoffman wrote:
Christian Ehrlicher wrote:
* We're using an NMake build tree, is NMake particularly
slow? Do any of the other makes work more efficiently?
Be aware that nmake builds are much slower than using devenv, as nmake
starts a cl.exe process for every single file,
2007/12/11, Jason Stewart [EMAIL PROTECTED]:
This is not scientific but I wrote a quick perl script to compile a
simple library that we use (GCTPc). It consists of 70 C files with most
of the files between 5K and 6K, a few are as large as 70K. The script
just uses the time() function to grab
* We're using an NMake build tree, is NMake particularly
slow? Do any of the other makes work more efficiently?
Be aware that nmake builds are much slower than using devenv, as nmake starts a
cl.exe process for every single file,
whereas devenv calls cl.exe with several source
On Dec 11, 2007 8:16 AM, Bill Hoffman [EMAIL PROTECTED] wrote:
Jian Wang wrote:
Why is IF(${VARIABLE} MATCHES ^${VARIABLE}$) used instead of IF(
${VARIABLE} STREQUAL ${VARIABLE} ) (which would always return true)?
I'm not sure of use case but I'd say it's checking for special
Hello CMake users developers,
I've been trying to build ITK on my machine, and obviously is not related to
what is built, and CMake produces
some errors at the configuration step. Perhaps someoneelse has already
encountered
similar type of problem ?
My setup:
Windows XP, ITK 3.4.0 Latest
CMake 2.4.4 had some serious flaws and was only available for a very short
time before being fixed by 2.4.5
Update to the latest CMake release (2.4.7) and try again.
And don't forget to start over with an empty binary directory after updating
CMake...
HTH,
David
On 12/11/07, Cem DEMiRKIR
It's something more than just this simple example... I've tried it with
CMake 2.4.5, 2.4.7 and today's CVS CMake and it does not happen on my
machine. (The Debug C always properly links to Ad only, not also to A...)
I am using VS 2005 standard edition.
The problem was occurring on the ParaView3
A co-worker sees it on his Windows box (VS 7.1), but I don't on mine (VS 8).
So I don't know how to trigger it on Windows.
But I see it consistent for me on Linux, both with that simple example and
ParaView. Of course, I don't see the msvcrt(d) link warnings.
Clint
On Tuesday 11 December
Tristan, I have been slow to respond to your e-mail because it took a long
time to investigate the java problems created by your patch. Details,
below.
On 2007-12-11 10:59+0100 Tristan Carel wrote:
On Dec 10, 2007 8:58 PM, Alan W. Irwin [EMAIL PROTECTED] wrote:
Tristan, since you do not
Is there any way to turn off try compile during configuration?
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
26 matches
Mail list logo
