Hiya,
I'm using cmake in koffice and I work in a small library currently which
is located in a subdir and it depends on nothing else in the project.
I'm highly annoyed that each time I type make cmake takes about a minute
before it actually decided what to do, thrashing my HD the whole time.
Title: cmake 2.4.2 and qt 2.3nc
-Ursprüngliche Nachricht-
Von: Zein Salah
Gesendet: Mittwoch, 24. Mai 2006 14:02
An: ITK Users (E-Mail)
Betreff: cmake 2.4.2 and qt 2.3nc
Hello,
I have newly built my qt-itk project with cmake 2.4.2.
cmake generates a message: Multiple
Hi everyone :)
I am at last enjoying new 2.4 feature on BSD :D many thanks to all those who
made that possible.
I am using Cmake to find few dependencies for some personal projects.
I setup correctly the CMAKE_INCLUDE_PATH and CMAKE_LIBRARY_PATH to get all my
SDL_* dependencies found and
At 07:30 AM 5/26/2006, Thomas Zander wrote:
Hiya;
In KDE (including KOffice) we switched to cmake, as you are probably
aware. I naturally like the speedups we got in linking etc. but I like
the less then stellar usability of the cmake solution a lot less. (at
this point I would gladly go back
On Friday 26 May 2006 16:24, you wrote:
I am not sure I understand what you want to type to do the build?
williamMake would do; of wmake if you want. :)
Bottom line; I don't care what the name is as long as it _can_ be made
more usable. Which is impossible with make.
You apparently are
On Friday 26 May 2006 16:28, you wrote:
If you only want to build a target, then run make targetname/fast it
will skip all of the depend steps, and only build that target.
Doesn't seem to work here on my 2.4-p2
--
Thomas Zander
pgpqR2sSorTIU.pgp
Description: PGP signature
Asmodehn Shade wrote:
I am using Cmake to find few dependencies for some personal projects.
I setup correctly the CMAKE_INCLUDE_PATH and CMAKE_LIBRARY_PATH to get all my
SDL_* dependencies found and working fine.
But I also in my script do a simple : FIND_PACKAGE(OpenGL)
And when doing a
Thomas Zander wrote:
On Friday 26 May 2006 16:28, you wrote:
If you only want to build a target, then run make targetname/fast it
will skip all of the depend steps, and only build that target.
Doesn't seem to work here on my 2.4-p2
Try it in the top level instead of the subdir. It looks
Thomas Zander wrote:
On Friday 26 May 2006 16:24, you wrote:
I am not sure I understand what you want to type to do the build?
williamMake would do; of wmake if you want. :)
Bottom line; I don't care what the name is as long as it _can_ be made
more usable. Which is impossible with make.
On Friday 26 May 2006 17:05, Thomas Zander wrote:
On Friday 26 May 2006 16:24, you wrote:
I am not sure I understand what you want to type to do the build?
williamMake would do; of wmake if you want. :)
Bottom line; I don't care what the name is as long as it _can_ be made
more usable.
At 11:05 AM 5/26/2006, Thomas Zander wrote:
On Friday 26 May 2006 16:24, you wrote:
I am not sure I understand what you want to type to do the build?
williamMake would do; of wmake if you want. :)
Bottom line; I don't care what the name is as long as it _can_ be made
more usable. Which is
On Friday 26 May 2006 17:52, Craig Bradney wrote:
On Friday 26 May 2006 17:05, Thomas Zander wrote:
On Friday 26 May 2006 16:24, you wrote:
I am not sure I understand what you want to type to do the build?
williamMake would do; of wmake if you want. :)
Bottom line; I don't care what
On Friday 26 May 2006 17:55, you wrote:
A 'configure' script generator that will just convert between the
(good old) configure and the cmake foo. Makes it actually possible
to discover what features there are without consulting online
documentation ;)
I am not sure about what you want
You can use CONFIGURE_FILE to copy the file:
IF(CMAKE_CONFIGURATION_TYPES)
# Handle multi-configuration generators.
FOREACH(config ${CMAKE_CONFIGURATION_TYPES})
CONFIGURE_FILE(${CMAKE_CURRENT_SOURCE_DIR}/my.config.in,
${CMAKE_CURRENT_BINARY_DIR}/${config}/my.config)
Hi,Recently a bug fix was made to VS.Net 2003 generator to allow source files with the same.The fix was to specify an ObjectFile for each and every source file, so that they would be guaranteed to be unique.
Unfortunately, even with CMAKE_VERBOSE_MAKEFILE set to FALSE, what you end up with now is
Yo Thomas,
We use cmake to build a large project (10 or so different SDKs).
In our case, we too wanted a cmakebuild tool, so we wrote one.
It wraps the native build tools with a higher level of commands
build debug build release run tests package SDKs etc.
Some of the commands for this build
Lloyd Hilaiel wrote:
Yo Thomas,
We use cmake to build a large project (10 or so different SDKs).
In our case, we too wanted a cmakebuild tool, so we wrote one.
It wraps the native build tools with a higher level of commands
build debug build release run tests package SDKs etc.
Some of
Steve Johns wrote:
Excellent! Thanks very much for this info.
I'm seeing a problem, though.
CMake is not finding my config file, even though it does exist.
CMake announces its search with forward-slash paths, but I'm in the VS
C++ IDE.
Is CMake not actually looking for:
Steve Johns wrote:
What is the exact CONFIGURE_FILE call you are using?
Here it is, cut and pasted:
IF(CMAKE_CONFIGURATION_TYPES)
# Handle multi-configuration generators.
FOREACH(config ${CMAKE_CONFIGURATION_TYPES})
CONFIGURE_FILE(${CMAKE_CURRENT_SOURCE_DIR}/traps_config.txt,
On Friday 26 May 2006 18:50, [EMAIL PROTECTED] wrote:
Actually, I wonder why CMAKE_VERBOSE_MAKEFILE is not set to TRUE by
default, each time, I have to set it manually and I find it quite
annoying.
It is a matter of taste. Some folks like to see pages and pages of output
even if it
On Friday 26 May 2006 18:02, frederic heem wrote:
Actually, I wonder why CMAKE_VERBOSE_MAKEFILE is not set to TRUE by
default, each time, I have to set it manually and I find it quite
annoying.
Everyone I know gave a sigh of relieve when unsermake (2 years ago)
introduced the concept of
Thomas Zander wrote:
Its because it slows me down a lot.
When I change a couple of header files I suddenly see it reconfiguring for
no apparent reason.
Its when I type 'make' it takes upto a minute before it actually starts
with the first gcc, even if I typed make moments before. (I just
Thomas Zander wrote:
I have helped a set of people on irc to get started with koffice compiling
using cmake. They all had a lot of problems with the arcane variables
like the CMAKE_INSTALL_PREFIX and most people find that D in front a bit
weird a well.
So; instead of letting the user
actually, I have found if I change the following entry (add expat to the linker flags) in cmxmlrpc/CMakeLists.txt this problem goes away:TARGET_LINK_LIBRARIES(xrtest cmXMLRPC cmexpat expat ${CMAKE_DL_LIBS})
On 5/26/06, Doug Henry [EMAIL PROTECTED] wrote:
I receive the errors below when building
Doug Henry wrote:
actually, I have found if I change the following entry (add expat to the
linker flags) in cmxmlrpc/CMakeLists.txt this problem goes away:
TARGET_LINK_LIBRARIES(xrtest cmXMLRPC cmexpat expat ${CMAKE_DL_LIBS})
From where is that other expat library coming? I bet the build of
Filipe Sousa wrote:
There is always ccmake and cmakeseup. Another option is to create a tool
called "cconfigure" for those who like configure scripts. That shouldn't
be to hard to implement. cconfigure --help would show the same options
as ccmake:
$ ./cconfigure --help
--cmake_build_type
There was a typo in my example: it should not have the comma between the
arguments. The trailing comma is being considered part of the file name!
Great eye, Brad!
So, here what I have now:
IF(CMAKE_CONFIGURATION_TYPES)
# Handle multi-configuration generators.
FOREACH(config
At 03:47 PM 5/26/2006, Steve Johns wrote:
IF(CMAKE_CONFIGURATION_TYPES)
# Handle multi-configuration generators.
FOREACH(config ${CMAKE_CONFIGURATION_TYPES})
CONFIGURE_FILE(${CMAKE_CURRENT_SOURCE_DIR}/traps_config.in
${CMAKE_CURRENT_BINARY_DIR}/${config}/traps_config.txt
What is the correct way to set the install RPATH under
CMake 2.4.2? At the moment I do the following within my
project's top most CMakeLists.txt file:
SET(CMAKE_BUILD_WITH_INSTALL_RPATH TRUE)
SET(CMAKE_INSTALL_RPATH ${CMAKE_INSTALL_PREFIX}/lib)
And the RPATH refuses to show itself in the
This is the point where we say: just don't do in-source builds... :-)
Use separate directories for source and binary trees.
2 cents,
David
Brad King wrote:
Steve Johns wrote:
ELSE(CMAKE_CONFIGURATION_TYPES)
# Handle single-configuration generators.
At 05:03 PM 5/26/2006, Axel Roebel wrote:
cmake --help
cmake variables
--build_type Choose the type of build, options are: ...
--install_prefix Install path prefix, prepended onto install directories
--verbose_make If this value is on, makefiles will be
project options
--USE_FOOBAR
Has anyone managed to build OpenSSL with CMake?
(I'm not looking for FindOpenSSL - I want to build the package itself)
James
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
32 matches
Mail list logo