Re: [CMake] cmake-gui leaves CMAKE__COMPILER_WORKS undefined for simple test case and CMake-2.6.4

On 2009-07-15 22:54-0600 Clinton Stimpson wrote: I don't have much to say except that ccmake behaves the same as cmake-gui in this case. You can add this at the end to see it. set(MYSTATUS ${CMAKE_CXX_COMPILER_WORKS} CACHE STRING "") Thanks for pointing that out. This can of worms just kee

Re: [CMake] cmake-gui leaves CMAKE__COMPILER_WORKS undefined for simple test case and CMake-2.6.4

On 2009-07-15 18:33-0700 Alan W. Irwin wrote: But then one of our developers made the mistake of trying cmake-gui which left CMAKE__COMPILER_WORKS undefined in all cases and which therefore caused many build problems. I can hack around that cmake-gui bug by simply setting CMAKE__COMPILER_WORKS

Re: [CMake] cmake-gui leaves CMAKE__COMPILER_WORKS undefined for simple test case and CMake-2.6.4

I don't have much to say except that ccmake behaves the same as cmake-gui in this case. You can add this at the end to see it. set(MYSTATUS ${CMAKE_CXX_COMPILER_WORKS} CACHE STRING "") Clint On 07/15/2009 07:33 PM, Alan W. Irwin wrote: Here is a simple CMakeLists.txt test case that reveals wh

Re: [CMake] "continue" to find file with find_file

You could try forcing the cache entry for the path to XXX_PATH-NOTFOUND (or unset(XXX_PATH CACHE)) and by using GET_FILENAME_COMPONENT() try to remove the path where the directory was found from a list that you're passing into the find_path() call. This probably wouldn't work for things specified

[CMake] cmake-gui leaves CMAKE__COMPILER_WORKS undefined for simple test case and CMake-2.6.4

Here is a simple CMakeLists.txt test case that reveals what I believe is a cmake-gui language bug. # stanza 1 project(test NONE) cmake_minimum_required(VERSION 2.6.4) # stanza 2 include(CMakeDetermineCXXCompiler) message(STATUS "CMAKE_CXX_COMPILER = ${CMAKE_CXX_COMPILER}") #stanza 3 enable_lang

Re: [CMake] Processing the output from CMake build

2009/7/15 Dieter Oberkofler : >> Since the build is done by the target generator >> (make, nmake, etc...) I would say the change should >> be made in each generator you are wanting to support/use >> beginning with Makefile generator. > This is correct. > >> 1) On first invocation of CMake force the

[CMake] Why do NSIS installers created by CMake/CPack trigger the Program Compatibility Wizard under Vista?

Hello! I am using CMake/CPack to create NSIS installers for 64-bit Windows Vista programs. Every time I run the installer on a 64-bit Windows Vista Ultimate SP2 machine, I trigger the Program Compability Wizard - it says that it has detected that "older code" is being installed, and wants to k

Re: [CMake] Processing the output from CMake build

> Since the build is done by the target generator > (make, nmake, etc...) I would say the change should > be made in each generator you are wanting to support/use > beginning with Makefile generator. This is correct. > 1) On first invocation of CMake force the compiler to be yours: > > $ CC=filec

Re: [CMake] Processing the output from CMake build

This does sound very interesting but I'm not sure if I understand how this might replace my need for a wrapper. To better understand, it would be most helpful, if you could eventually post a short CMakeLists.txt snipped on how to capture the output from a compile/link using CTEST_USE_LAUNCHERS. Th

Re: [CMake] cmake giving errors while building kdelibs svn

On Wednesday 15 July 2009, Primal Pappachan wrote: > 2009/7/15 Alexander Neundorf ... > > Which version of cmake are you using ? > > How do you run cmake ? (i.e. which arguments etc.) > > Usually it should be enough to run > > cmake -DCMAKE_INSTALL_PREFIX= > > > > No additional arguments should b

Re: [CMake] Shared libraries cannot be found after deploying a CPack package

Am Mittwoch 15 Juli 2009 17:20:25 schrieb Frank Stappers: > With the help of CPack we would like to make packages. Currently, > we can make packages for MAC OSX (DMG, TSGZ, GZ) and UNIX (RPM, DEB, > STGZ, GZ). For static builds (so no shared libraries) these packages > can be deployed in any direct

Re: [CMake] Eclipse generator - basic macros

Am Mittwoch 15 Juli 2009 17:21:38 schrieb Mike Jackson: > On Wed, Jul 15, 2009 at 2:18 AM, Hendrik Sattler wrote: > > Zitat von Benjamin Schindler : > >> I'm working on a project which builds both on linux and windows. I > >> generated an eclipse project out of it which works basically fine but >

Re: [CMake] alternative library names?

Alright, after having found http://www.cmake.org/cmake/help/cmake2.6docs.html#command:find_library aka tfm (as is rtfm) is was pretty straightforward. Sorry for the noise! Cheers, Nico On Wednesday 15 July 2009 18:42:20 you wrote: > Hi, > > I'm using CMake for a program that links against comm

Re: [CMake] alternative library names?

On Wed, Jul 15, 2009 at 06:56:40PM +0200, Michael Wild wrote: > find_library( FOOBAR_LIBRARY NAMES foobar myfoobar yourfoobar ) I was faster, but this is better :). tyler ___ Powered by www.kitware.com Visit other Kitware open-source projects at http:

Re: [CMake] alternative library names?

On 15. Jul, 2009, at 18:42, Nico Schlömer wrote: Hi, I'm using CMake for a program that links against common libraries which may happen to have different names on different architectures (e.g., libfoobar.a, libmyfoobar.a, libyourfoobar.a,...). Until now I was always searching for libs lik

Re: [CMake] alternative library names?

On Wed, Jul 15, 2009 at 06:42:20PM +0200, Nico Schlömer wrote: > I'm using CMake for a program that links against common libraries which may > happen to have different names on different architectures (e.g., libfoobar.a, > libmyfoobar.a, libyourfoobar.a,...). > > Until now I was always searching

[CMake] alternative library names?

Hi, I'm using CMake for a program that links against common libraries which may happen to have different names on different architectures (e.g., libfoobar.a, libmyfoobar.a, libyourfoobar.a,...). Until now I was always searching for libs like this = *snip* = find

Re: [CMake] Processing the output from CMake build

2009/7/15 Bill Hoffman > Eric Noulard wrote: >> >> 2009/7/15 Bill Hoffman : >>> >>> CVS CMake/CTest has a new wrapper mode that can be used.    It is set >>> with >>> CTEST_USE_LAUNCHERS=1. >> >> I'm not sure to understand that. >> How can it be used? >> What does it make? >> >> Is there some doc

Re: [CMake] Processing the output from CMake build

Eric Noulard wrote: 2009/7/15 Bill Hoffman : CVS CMake/CTest has a new wrapper mode that can be used.It is set with CTEST_USE_LAUNCHERS=1. I'm not sure to understand that. How can it be used? What does it make? Is there some doc for this ? On the Wiki ? In a source file? Doc's are comin

Re: [CMake] Processing the output from CMake build

2009/7/15 Bill Hoffman : > CVS CMake/CTest has a new wrapper mode that can be used.    It is set with > CTEST_USE_LAUNCHERS=1. I'm not sure to understand that. How can it be used? What does it make? Is there some doc for this ? On the Wiki ? In a source file? -- Erk Membre de l'April - « promo

Re: [CMake] Shared libraries cannot be found after deploying a CPack package

2009/7/15 Frank Stappers : > With the help of CPack we would like to make packages. Currently, > we can make packages for MAC OSX (DMG, TSGZ, GZ) and UNIX (RPM, DEB, > STGZ, GZ). For static builds (so no shared libraries) these packages > can be deployed in any directory, without any problems. For

[CMake] About using javac -d option from cmake

Hello, I would like to know how I can change the -d option for the javac tool from a cmake script. I do not know exactly which cmake variable is managing the .class target directory. Thanks for your help, Arnaud. ___ Powered by www.kitware.com Visit ot

Re: [CMake] Processing the output from CMake build

CVS CMake/CTest has a new wrapper mode that can be used.It is set with CTEST_USE_LAUNCHERS=1. -Bill ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages

[CMake] "continue" to find file with find_file

Hi, I am currently writing a FindXXX.cmake file which uses find_path to find an include path. Unfortunately it turns out that there might be several versions of the file in the PATHs/HINTS (e.g. several revisions of the package). (I handle this with test using the try_compile command). My ques

Re: [CMake] Processing the output from CMake build

2009/7/15 Dieter Oberkofler : >> But I do not need that feature, would you explain why >> you need the 1 file compiled - 1 file error mapping? > Generally speaking to keep track of each individual file status. This > especially useful, when dealing with compiler warnings that would simply > "disapp

[CMake] Shared libraries cannot be found after deploying a CPack package

With the help of CPack we would like to make packages. Currently, we can make packages for MAC OSX (DMG, TSGZ, GZ) and UNIX (RPM, DEB, STGZ, GZ). For static builds (so no shared libraries) these packages can be deployed in any directory, without any problems. For builds that use shared libraries, t

Re: [CMake] Eclipse generator - basic macros

On Wed, Jul 15, 2009 at 2:18 AM, Hendrik Sattler wrote: > Zitat von Benjamin Schindler : >> >> I'm working on a project which builds both on linux and windows. I >> generated an eclipse project out of it which works basically fine but >> it's not able to recognize i.e. the __GNUC__ macro (and proba

Re: [CMake] Processing the output from CMake build

> I usually edit in some editors (vi, [x]emacs, eclipse etc...) > and use command line a lot too. I use BBEdit or the XCode editor on the Mac and CodeWright (an amazing editor for programmer that after being sold to Borland some years ago is unfortunately no longer available) on the PC. > But I do

Re: [CMake] Equivalent to VERBOSE for nmake

Michael Jackson wrote: -Bill If I go editing Windows.cmake what ramifications will that have on generating normal Visual Studio project files? It will not affect Visual Studio IDE projects, but might break some nmake projects if the command lines get too long. -Bill _

Re: [CMake] CMake definition for using NMake files

Just needed a bit more time: CMAKE_GENERATOR Sorry for the noise. _ Mike Jackson mike.jack...@bluequartz.net BlueQuartz Softwarewww.bluequartz.net Principal Software Engineer Dayton, Ohi

Re: [CMake] Equivalent to VERBOSE for nmake

On Jul 15, 2009, at 9:38 AM, Bill Hoffman wrote: Michael Jackson wrote: Is there an equivalent to make VERBOSE=1 but for nmake files under windows? nmake VERBOSE=1. However, to get all the compile lines, you have to edit Platforms/Windows.cmake. # uncomment these out to debug nmake and

[CMake] CMake definition for using NMake files

Does CMake have a predefined definition like MSVC but when using NMake files? Thanks _ Mike Jackson mike.jack...@bluequartz.net BlueQuartz Softwarewww.bluequartz.net Principal Software Engineer

Re: [CMake] Equivalent to VERBOSE for nmake

Michael Jackson wrote: Is there an equivalent to make VERBOSE=1 but for nmake files under windows? nmake VERBOSE=1. However, to get all the compile lines, you have to edit Platforms/Windows.cmake. # uncomment these out to debug nmake and borland makefiles #SET(CMAKE_START_TEMP_FILE "") #SET

[CMake] Equivalent to VERBOSE for nmake

Is there an equivalent to make VERBOSE=1 but for nmake files under windows? Thanks _ Mike Jackson mike.jack...@bluequartz.net BlueQuartz Softwarewww.bluequartz.net Principal Software Engineer

Re: [CMake] File-specific build directives

> cmake --help-command set_source_files_properties Thanks a lot Michael. Cheers, Manu ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and chec

Re: [CMake] File-specific build directives

On 15. Jul, 2009, at 13:56, eblo...@free.fr wrote: Hi, What is the best way, in a CMakeLists.txt file, to define specific build directive(s) for one or more C/C++ files, while other files are built with the default directives? As an example, how to apply "-O2" for one or more files, whil

Re: [CMake] Processing the output from CMake build

2009/7/15 Dieter Oberkofler : > I might sound old fashioned but I'm still only building from the command > line and only use an IDE (XCode on Mac and VS on the PC) when debugging. OK, command line is great :-) I usually edit in some editors (vi, [x]emacs, eclipse etc...) and use command line a lot

[CMake] File-specific build directives

Hi, What is the best way, in a CMakeLists.txt file, to define specific build directive(s) for one or more C/C++ files, while other files are built with the default directives? As an example, how to apply "-O2" for one or more files, while building the remaining file with "-Os"? TIA, Manu

[CMake] Processing the output from CMake build

I might sound old fashioned but I'm still only building from the command line and only use an IDE (XCode on Mac and VS on the PC) when debugging. I therefore manually changed the CMake compile and link rules to always generate an error file for each file that gets compiled or linked. This is quite

Re: [CMake] Problem with design and ADD_SUBDIRECTORY

Zitat von Martin Santa Maria : Thanks to all for your answers. The thing is that I don't want to code statically the existence of packages in the root/CMakeLists.txt but I want that each package register it-self in some "package container" that the CMakeLists.txt could read. This container shou

Re: [CMake] Problem with design and ADD_SUBDIRECTORY

Thanks to all for your answers. The thing is that I don't want to code statically the existence of packages in the root/CMakeLists.txt but I want that each package register it-self in some "package container" that the CMakeLists.txt could read. This container should be seen as a set of lists and