[CMake] cmakesetup.exe

Okay, first time trying cmake under windows, porting a project from linux. I'm trying to just create a simple cmake file for vc7.1. I downloaded the pre-built cmake (cmake 2.4 - patch 6). When I run CmakeSetup.exe, there's no option to allow me to select what build to create, as shown in the we

Re: [CMake] Module FindTCL behaves differently on Linux and Mac OS X

Clark J. Wang wrote: In my Ubuntu Linux box, after INCLUDE(FindTCL) I get the following result: TCL_INCLUDE_PATH = /usr/include/tcl8.4 TCL_LIBRARY = /usr/lib/libtcl8.4.so But in my Mac OS X 10.4 the result is: TCL_INCLUDE_PATH = /System/Library/Frameworks/Tcl.framework/Headers TCL_LIBRAR

Re: [CMake] Module FindTCL behaves differently on Linux and Mac OS X

On 5/18/07, Alan W. Irwin <[EMAIL PROTECTED]> wrote: On 2007-05-18 11:00+0800 Clark J. Wang wrote: > In my Ubuntu Linux box, after INCLUDE(FindTCL) I get the following result: > > TCL_INCLUDE_PATH = /usr/include/tcl8.4 > TCL_LIBRARY = /usr/lib/libtcl8.4.so > > > But in my Mac OS X 10.4 the

Re: [CMake] Module FindTCL behaves differently on Linux and Mac OS X

On 2007-05-18 11:00+0800 Clark J. Wang wrote: In my Ubuntu Linux box, after INCLUDE(FindTCL) I get the following result: TCL_INCLUDE_PATH = /usr/include/tcl8.4 TCL_LIBRARY = /usr/lib/libtcl8.4.so But in my Mac OS X 10.4 the result is: TCL_INCLUDE_PATH = /System/Library/Frameworks/Tcl.fr

[CMake] Module FindTCL behaves differently on Linux and Mac OS X

In my Ubuntu Linux box, after INCLUDE(FindTCL) I get the following result: TCL_INCLUDE_PATH = /usr/include/tcl8.4 TCL_LIBRARY = /usr/lib/libtcl8.4.so But in my Mac OS X 10.4 the result is: TCL_INCLUDE_PATH = /System/Library/Frameworks/Tcl.framework/Headers TCL_LIBRARY = /System/Libra

[CMake] Re: Using ADD_CUSTOM_COMMAND to generate sources...

(Ick, top-posting...) Ken Martin wrote: Matthew Woehlke wrote: Ok... so I see that ADD_CUSTOM_COMMAND is silently ignored if no targets depend on the OUTPUT. What is strange is that the output is #include'd from one of my source files, and I can see from looking at the generated CMakeFiles/my

RE: [CMake] Using ADD_CUSTOM_COMMAND to generate sources...

Well CMake does not /really/ know about the dependency :) Because the dependency is done through #include in the source code it is not known at CMake Configure/Generate time. Dependency analysis of source code is done at build time. For "make" based builds CMake does this during the build process (

RE: [CMake] Bug in ADD_LIBRARY (again?)

The fix to ADD_LIBRARY is in CVS and has not been put into a patch yet. It should make it into 2.4.7. 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 Guilherme Balen

[CMake] submission: updated Modules/FindBoost.cmake

boost recently updated to 1.34, changing (of course) the default installation path. this breaks the FindBoost cmaker, so attached is an update that allows 1.34 as released to work. FindBoost.cmake Description: Binary data ___ CMake mailing list CM

[CMake] CMake Project With just CMakeLists.txt files

Is there anyway to create a project that contains only the CMakeLists.txt file without any sources/headers? We have an external Plugins directory within our repository which we do not want to combine with the core programs sources. Directory Structure Plugins_dir -> plugin 1 subdirectory -

[CMake] Bug in ADD_LIBRARY (again?)

Hello, The ADD_LIBRARY does not understand EXCLUDE_FROM_ALL in CMake version 2.4 patch 6. I found a message from Ken Martin dated from Jan/4/2007 saying "Yup, I'll check in a fix for it". For which version did this fix go? Or, maybe, are there no available fixed release yet? Regards, Guilhe

Re: [CMake] fortran, modules and case

Alan W. Irwin wrote: > I should also mention that for the simple example I attached to the > previous > e-mail the gfortran library build does produce a valid module file called > hello_module.mod. > > So it appears bug 3984 is just caused by CMake assuming the module file > name > is MODULENAME.m

Re: [CMake] Re: Finding libraries under Windows

Leon Moctezuma wrote: Thanks Brandon and Mike I did something similar to Mike's code adn this wiki page[1 ]. I could see different things in Chiken, that helped me to understand cmake better. Here is the script: IIF(WIN32) FIND

Re: [CMake] Finding libraries under Windows

Leon Moctezuma wrote: Hi all. I'm Leon Moctezuma, a cs student, who is participating in GSoC and working on Freepv, we are trying to use cmake instead of autoconf for the projects building process we have been able to create a basic CMakeLists.txt under both Linux and Windows, It works almost

Re: [CMake] how to get compile environment ($host) in cmake

On 5/17/07, haibin zhang <[EMAIL PROTECTED]> wrote: thanks but I see cmake-2.4.6 CMakeLists.txt file : IF(WIN32) IF(NOT UNIX) IF(NOT BORLAND) IF(NOT MINGW ) SET(CMAKE_BUILD_ON_VISUAL_STUDIO 1) ENDIF(NOT MINGW ) ENDIF(NOT BORLAND) ENDIF(NOT UNIX) ENDIF(WIN32) who

[CMake] Re: different obj dirs for debug and release

Thanks! :) I was already using this method, and it works well. Now I use an external script to move into the debug and release folders and then launch cmake with the needed options to create the makefiles. I'm still wondering if there is a way to replace the script with a command inside a CMake

Re: [CMake] how to get compile environment ($host) in cmake

thanks but I see cmake-2.4.6 CMakeLists.txt file : IF(WIN32) IF(NOT UNIX) IF(NOT BORLAND) IF(NOT MINGW ) SET(CMAKE_BUILD_ON_VISUAL_STUDIO 1) ENDIF(NOT MINGW ) ENDIF(NOT BORLAND) ENDIF(NOT UNIX) ENDIF(WIN32) who set this , WIN32 or UNIX or other ? regards "Clark

Re: [CMake] how to get compile environment ($host) in cmake

On 5/17/07, haibin zhang <[EMAIL PROTECTED]> wrote: Hi all : how to get $host in cmake ? In autotool , it can use $host to get compile environment, example cygwin,i686-pc-mingw32 . Use CMAKE_SYSTEM regards -- Mp3疯狂搜-新歌热歌高速下