Original-Nachricht
Datum: Tue, 11 Jul 2006 12:45:16 +0930
Von: Patrick Noffke [EMAIL PROTECTED]
An: cmake@cmake.org
Betreff: [CMake] Dependency on CONFIGURE_FILE output
How do I create a dependency on the output of a CONFIGURE_FILE operation?
I tried adding the output file as
Peter Kahn wrote:
I've been looking for a good cross platform build/project definition
system for some time. I have built my own, looked at Scons and Cmake.
Cmake's support for the various IDEs upon which my developers wish to
work has tipped the balance. I've read through Mastering Cmake
Hi there
I'm developing and compiling KDE using cmake and I really like it and would
choose it any day over auto*, but I have this small nag.
Say I've changed a headerfile somewhere which in a complete build would cause
lots of files to be recompiled and linked.
That is fine, but now imagine
Casper Boemann wrote:
That used to work during the auto* days, but with cmake it begins to recompile
everywhere else too. That means i send a lot of time recompiling stuff i
don't need (until later)
That's annoying e, too - I vote for this ;-)
I don't know how to fix it but it is related
At 09:05 AM 7/11/2006, Casper Boemann wrote:
Hi there
I'm developing and compiling KDE using cmake and I really like it and would
choose it any day over auto*, but I have this small nag.
Say I've changed a headerfile somewhere which in a complete build would cause
lots of files to be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My directory structure is something like this
root/
|-proj1/
| |-share
|
|-proj2/
|-share
My top level CMakeLists.txt is in proj1 using proj2 with SUBDIRS(
proj2 ) to compile some libraries placed in
Hello,
I'm using the STLport library on several targets on my project, and need to
define the _STLP_DEBUG flag on the debug configuration of each target. I looked
at :
SET_TARGET_PROPERTIES ( PROPERTIES COMPILE_FLAGS -D_STLP_DEBUG )
... but it doesn't seem to be able to specify a switch for a
Sagnes, Frederic wrote:
Hello,
I'm using the STLport library on several targets on my project, and need to
define the _STLP_DEBUG flag on the debug configuration of each target. I looked
at :
SET_TARGET_PROPERTIES ( PROPERTIES COMPILE_FLAGS -D_STLP_DEBUG )
... but it doesn't seem to be able
Sagnes, Frederic wrote:
Hello,
I'm using the STLport library on several targets on my project, and need to
define the _STLP_DEBUG flag on the debug configuration of each target. I looked
at :
SET_TARGET_PROPERTIES ( PROPERTIES COMPILE_FLAGS -D_STLP_DEBUG )
... but it doesn't seem to be able
Alex Makarenko wrote:
Using \${CTEST_CONFIGURATION_TYPE} works. Is there some official document
where I could look up these variables in the future?
There is some documentation in the CMake book. There is also a
user-maintained list here:
http://www.cmake.org/Wiki/CMake_Useful_Variables
Christian Verbeek wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My directory structure is something like this
root/
|-proj1/
| |-share
|
|-proj2/
|-share
My top level CMakeLists.txt is in proj1 using proj2 with SUBDIRS(
proj2 ) to
Furthermore could it be made so that the default target in subdirs are
fast
and that you'd have to write something special (like /slow) to make it
like
today.
Personally I tend not to like having the default option be fast (aka unsafe)
although we have debated both sides of it. To me the
These bugs are as of cmake 2.4. patch 2 (branch CMake-2.4)
Bug 1:
Linking against QT built as static is incorrect under windows, patch was
posted some time ago, but am still waiting
http://www.cmake.org/Bug/bug.php?op=showbugid=3222pos=27
also Qt static needs imm32 ws_32 and something else I
Why is FindPythonInterp called that rather than FindPython? Would be
more in line with others (FindPerl, FindRuby), etc.
--
Orion Poplawski
System Administrator 303-415-9701 x222
Colorado Research Associates/NWRA FAX: 303-415-9702
3380 Mitchell Lane, Boulder CO 80301
Orion Poplawski wrote:
Why is FindPythonInterp called that rather than FindPython? Would be
more in line with others (FindPerl, FindRuby), etc.
This is historical. No one has contributed a real FindPython that uses
disutils:
http://www.cmake.org/Bug/bug.php?op=showbugid=2257
-Brad
I do not see a patch attached to that bug report. Is there a bug report
that has a patch attached to it?
At 12:47 PM 7/11/2006, John Biddiscombe wrote:
These bugs are as of cmake 2.4. patch 2 (branch CMake-2.4)
Bug 1:
Linking against QT built as static is incorrect under windows, patch was
On Tuesday 11 July 2006 17:56, you wrote:
To me the naïve
invocation should be safe and the special invocation should be the unsafe
one.
Ok I wouldn't mind if slow is default as long as:
make fast
would work anywhere (doing the local target/fast)
Actually I ve come across a problem with
Jorge Rodriguez wrote:
I am having some problems building a 64 bit version of my application
using the NMake generator on 64 bit Windows with Visual Studio 8.0.
I am using the Microsoft Platform SDK command prompts that can be opened
through the start menu. I can use the Visual Studio 8 2005
Brad King wrote:
Thanks. Did your VS come with a
Visual Studio 2005 x64 Win64 Command Prompt
No. Maybe I didn't install 64 bit building?
? What installed/configured the other prompts?
Microsoft Platform SDK February 2003, and Microsoft Platform SDK for
Windows Server 2003 SP1
--
Brad King wrote:
Jorge Rodriguez wrote:
Brad King wrote:
Thanks. Did your VS come with a
Visual Studio 2005 x64 Win64 Command Prompt
No. Maybe I didn't install 64 bit building?
This may be the case. Also, is this VS 2005 Professional or the
VCExpress version?
Pro. I looked on my
Hello
I recently used cmake for a project.
So I added a line like this to my CMakeLists.txt:
PROJECT(ProjectName CXX)
Later on, when i tested the build-environment
i saw error lines like this:
cd /some/directory cr libFOO.a CMakeFiles/FOO.dir/Foo.o
Now this is the line of the Makefile where
Philipp Meinen wrote:
Hello
I recently used cmake for a project.
So I added a line like this to my CMakeLists.txt:
PROJECT(ProjectName CXX)
Later on, when i tested the build-environment
i saw error lines like this:
cd /some/directory cr libFOO.a CMakeFiles/FOO.dir/Foo.o
Now this
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Behalf Of
Alexander Neundorf
Sent: Tuesday, 11 July 2006 4:21 PM
To: Patrick Noffke; cmake@cmake.org
Subject: Re: [CMake] Dependency on CONFIGURE_FILE output
Original-Nachricht
Datum:
There is some documentation in the CMake book. There is also a
user-maintained list here:
http://www.cmake.org/Wiki/CMake_Useful_Variables
We would like to auto-generate documentation for variables as is done
for commands but it is not yet implemented.
Thanks Brad, an exhaustive list with
24 matches
Mail list logo
