[CMake] CMake support for Itanium builds with Visual Studio 2005

We need to build our software for Windows Itanium. For this we use Microsoft Visual Studio 2005 with cross tools to generate executables for x86_amd64 and x86_ia64. Compiling for x86_amd64 works fine with CMake but the x86_ia64 fails. Does somebody have a clue on howto fix this or that can

[CMake] Setting STATIC_LIBRARY_FLAGS for different configurations

Hi I am building some libraries using CMake. I am setting STATIC_LIBRARY_FLAGS property of the targets using SET_TARGET_PROPERTIES. Now is there a provision in CMake by which I can assign different values to STATIC_LIBRARY_FLAGS for a target in the Debug and Release configurations.For e.g.

[CMake] cmake (no longer?) complains about missing files

Hi, I don't know if it's the intended behaviour or not: I create a file on build time with add_custom_command. ADD_CUSTOM_COMMAND(OUTPUT ${CMAKE_BINARY_DIR}/my_source.cpp COMMAND makeMySource ARGS ${CMAKE_BINARY_DIR}/my_source.cpp ) and add it to an executable:

Re: [CMake] MACOSX_BUNDLE targets fail as custom target dependencies

Allan Odgaard wrote: I have the following CMakeLists.txt file: project(foo) add_executable(foo MACOSX_BUNDLE main.cc) add_custom_target(run_foo echo running foo DEPENDS foo) This is what I get (Mac OS X Leopard, CMake 2.6.0 and 2.7 from CVS): % make run_foo

Re: [CMake] cmake (no longer?) complains about missing files

Christian Ehrlicher wrote: I don't know if it's the intended behaviour or not: I create a file on build time with add_custom_command. ADD_CUSTOM_COMMAND(OUTPUT ${CMAKE_BINARY_DIR}/my_source.cpp COMMAND makeMySource ARGS ${CMAKE_BINARY_DIR}/my_source.cpp ) and add it

[CMake] Thanks

Sorry if there's a better forum for this message, but I thought this would reach the most CMake developers and module maintainers... Thanks! CMake has saved me lots and lots of time, and made my work more enjoyable. I had a large (by my standards) C++ project that ran on Linux. Switching to

Re: [CMake] MACOSX_BUNDLE targets fail as custom target dependencies

Am Dienstag 27 Mai 2008 15:56:14 schrieb Brad King: Allan Odgaard wrote: project(foo) add_executable(foo MACOSX_BUNDLE main.cc) add_custom_target(run_foo echo running foo DEPENDS foo) [snip] Without the MACOSX_BUNDLE setting of the target, or trying to build the same project

Re: [CMake] Thanks

Convey Christian J NPRI wrote: Sorry if there's a better forum for this message, but I thought this would reach the most CMake developers and module maintainers... Thanks! CMake has saved me lots and lots of time, and made my work more enjoyable. I had a large (by my standards) C++ project

[CMake] another target with the same name exists

Am I insane, or is CMake? In a subdirectory of our big ol build tree, CMake is freaking out about duplicate targets in a way that makes no sense to me: CMake Error at src/iplProg/AutoSeg/ProcessDescription/CMakeLists.txt:3 (ADD_LIBRARY): add_library cannot create target ProcessDescription

Re: [CMake] Thanks

-Original Message- From: Bill Hoffman [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2008 11:06 AM To: Convey Christian J NPRI Cc: cmake@cmake.org Subject: Re: [CMake] Thanks Convey Christian J NPRI wrote: Sorry if there's a better forum for this message, but I thought this

Re: [CMake] [PATCH] FindQt4.cmake qt4_automoc improvements

Again on the INCLUDE_DIRECTORIES(${QT_${module}_INCLUDE_DIR}) from UseQt4.cmake Since it is confirmed that Trolltech and kdelibs devs take care about the #include QtCore/Q... Will a patch like this would be OK? It simply add a variable set to ON by default. If OFF then UseQt4.cmake does not do

Re: [CMake] another target with the same name exists

kent williams wrote: Am I insane, or is CMake? In a subdirectory of our big ol build tree, CMake is freaking out about duplicate targets in a way that makes no sense to me: CMake Error at src/iplProg/AutoSeg/ProcessDescription/CMakeLists.txt:3 (ADD_LIBRARY): add_library cannot create target

Re: [CMake] [PATCH] FindQt4.cmake qt4_automoc improvements

On Tuesday 27 May 2008 9:53:34 am Tanguy Krotoff wrote: Again on the INCLUDE_DIRECTORIES(${QT_${module}_INCLUDE_DIR}) from UseQt4.cmake Since it is confirmed that Trolltech and kdelibs devs take care about the #include QtCore/Q... Yes, Qt does take care with their public headers to let you do

Re: [CMake] cmake (no longer?) complains about missing files

Brad King wrote: Christian Ehrlicher wrote: add_executable(myExecutable ${CMAKE_BINARY_DIR}/my_source.cpp) cmake does not complain when the file does not exist. For instance when I forgot the add_custom_command() or misspelled the filename. Instead I get an error from make. I know there

Re: [CMake] [PATCH] FindQt4.cmake qt4_automoc improvements

I'm curious what the timings are with and without the include paths. Can you give some data? If I remember right, this thread started by talking about compile times. That's right! I just tried on phonon-vlc-mplayer http://code.google.com/p/phonon-vlc-mplayer/ the timing argument just is not

[CMake] Problems to get start and Tutorials

Hello, I have much problems to get started with cmake (2.6.0). I edit a CMakeFiles.txt with the following content: (It's just al small windows application. And no special libs used.) ---snip--- PROJECT( mainapp ) SET( mainapp_SRCS mainapp.c ) ADD_EXECUTABLE( mainapp ${mainapp_SRCS} ) ---snap---