[CMake] CMake's Xcode generator seems to ignore the CMAKE_CXX_COMPILER variable

I would like to compile my project using the g++ 4.2 and with Xcode generator to use Xcode 3.1.2 as my IDE. If I call cmake like cmake -D CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/g++-4.2 -GXcode ../path/ to/source/tree I get a Xcode project that I can open with Xcode 3.1.2 but if I look at

Re: [CMake] CMake's Xcode generator seems to ignore the CMAKE_CXX_COMPILER variable

CXX=/usr/bin/g++-4.2 cmake -GXcode ../path/to/source/tree On Tue, Feb 24, 2009 at 3:20 PM, Stephan Aiche ai...@mi.fu-berlin.de wrote: I would like to compile my project using the g++ 4.2 and with Xcode generator to use Xcode 3.1.2 as my IDE. If I call cmake like cmake -D

Re: [CMake] CMake's Xcode generator seems to ignore the CMAKE_CXX_COMPILER variable

Thanks Mathieu for your fast reply. I've tested it and it does not work. My Xcode still tells me that it will use the GCC 4.0 as compiler. Stephan On Feb 24, 2009, at 3:22 PM, Mathieu Malaterre wrote: CXX=/usr/bin/g++-4.2 cmake -GXcode ../path/to/source/tree On Tue, Feb 24, 2009 at 3:20

Re: [CMake] CMake's Xcode generator seems to ignore the CMAKE_CXX_COMPILER variable

Was it in an empty directory or was there an already existing CMakeCache.txt referencing the other compiler ? On Tue, Feb 24, 2009 at 3:32 PM, Stephan Aiche ai...@mi.fu-berlin.de wrote: Thanks Mathieu for your fast reply. I've tested it and it does not work. My Xcode still tells me that it will

Re: [CMake] CMake's Xcode generator seems to ignore the CMAKE_CXX_COMPILER variable

It was an empty directory. Also inspecting the CMakeCache.txt shows //C++ compiler CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/g++-4.2 For me it seems, that the generator is ignoring this variable while generating the Xcode project files Stephan On Feb 24, 2009, at 3:35 PM, Mathieu Malaterre

Re: [CMake] CMake's Xcode generator seems to ignore the CMAKE_CXX_COMPILER variable

I do not have access to a Mac to replicate but I believe you. Technically this should have worked as I use this trick to specify a particular compiler instead of the default on a Visual Studio build. I guess there must be something wrong going on with Xcode. But I cannot help you anymore on this

Re: [CMake] CMake's Xcode generator seems to ignore the CMAKE_CXX_COMPILER variable

Stephan Aiche wrote: It was an empty directory. Also inspecting the CMakeCache.txt shows //C++ compiler CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/g++-4.2 For me it seems, that the generator is ignoring this variable while generating the Xcode project files Stephan That will not work with

Re: [CMake] CMake's Xcode generator seems to ignore the CMAKE_CXX_COMPILER variable

On 2/24/09 10:01 AM, Bill Hoffman said: That will not work with Xcode projects. I am not sure how you tell Xcode to use a different compiler. Any Xcode experts out there? The compiler choice is amongst the project/target settings. In an xcconfig file, you would use, for example: GCC_VERSION

Re: [CMake] CMake's Xcode generator seems to ignore the CMAKE_CXX_COMPILER variable

On Tue, Feb 24, 2009 at 4:23 PM, Sean McBride s...@rogue-research.com wrote: On 2/24/09 10:01 AM, Bill Hoffman said: That will not work with Xcode projects. I am not sure how you tell Xcode to use a different compiler. Any Xcode experts out there? The compiler choice is amongst the

Re: [CMake] CMake's Xcode generator seems to ignore the CMAKE_CXX_COMPILER variable

Since you can only choose the following compilers in Xcode (at least in the version i have seen) GCC 3.3 (GCC_VERSION = 3.3) GCC 4.0 (GCC_VERSION = 4.0) GCC 4.2 (GCC_VERSION = 4.2) LLVM GCC 4.2 (GCC_VERSION = com.apple.compilers.llvmgcc42) it seems reasonable (to me) to give also only this

Re: [CMake] CMake's Xcode generator seems to ignore the CMAKE_CXX_COMPILER variable

And what do we do when Apple releases GCC 4.3 or 4.4? Then CMake is broke again. Run the gcc -dumpversion to extract out exactly which version is being used. The code to do that is in lots of places. _ Mike Jackson

Re: [CMake] Unix make files and CMAKE_EXE_LINKER_FLAGS_RELEASE

Philip, Ok... so it works with the Build_Type thing set, but now with out it. I also I'm using XCode sometimes and it doesn't use the linker flags at all. -Neal It could be something simple like 1. The CMAKE_EXE_LINKER_FLAGS_config variable is somehow not in scope when you're calling

[CMake] CPack + NSIS: Dependencies between components

Hello, I have a question concerning component-based install with CPack and NSIS: Among others, I have a library libA and a component depending on that library, appA. Using CPACK_COMPONENT_APPA_DEPENDS I can achieve that libA is installed if I select appA. But: If appA is the only component

Re: [CMake] Unix make files and CMAKE_EXE_LINKER_FLAGS_RELEASE

On Tue, Feb 24, 2009 at 6:45 PM, Neal Meyer nme...@dottedzebra.com wrote: Philip, Ok... so it works with the Build_Type thing set, but now with out it. I also I'm using XCode sometimes and it doesn't use the linker flags at all. set(CMAKE_EXE_LINKER_FLAGS -L/no/build/type) ? Don't know

Re: [CMake] Unix make files and CMAKE_EXE_LINKER_FLAGS_RELEASE

That seems to be different from the Visual Studio Generator's implementation. I've got the following in my CMake for Windows builds. (using VS 2005) set( CMAKE_EXE_LINKER_FLAGS /MANIFEST /DEBUG /MACHINE:X86 CACHE STRING Flags used by the linker FORCE ) set( CMAKE_EXE_LINKER_FLAGS_DEBUG

[CMake] CMake 2.6-3.app and version numbers in .app name

Hi all, Back in early April 2008 we debated whether CMake's .app should be named simply CMake.app or something with the version number, like CMake 2.6-3.app. I just updated from 2.6.2 to 2.6.3, and went to rebuild my VTK. It now says: /bin/sh: /Applications/CMake 2.6-2.app/Contents/bin/cmake:

Re: [CMake] Compiling OpenGL application with CMake

This is a bit odd to me. Why would not everything be required? Are there situations in which you might not need a package? Maybe I can answer my own question... If you have 2 libraries A and B that do the same task maybe you can use different compile rules like you showed below, while if A is

Re: [CMake] CMake 2.6-3.app and version numbers in .app name

Sean McBride wrote: Hi all, Back in early April 2008 we debated whether CMake's .app should be named simply CMake.app or something with the version number, like CMake 2.6-3.app. I just updated from 2.6.2 to 2.6.3, and went to rebuild my VTK. It now says: /bin/sh: /Applications/CMake

Re: [CMake] Compiling OpenGL application with CMake

On Tue, Feb 24, 2009 at 8:48 PM, Andrea Tagliasacchi a...@cs.sfu.ca wrote: This is a bit odd to me. Why would not everything be required? Are there situations in which you might not need a package? Maybe I can answer my own question... If you have 2 libraries A and B that do the same task

Re: [CMake] Compiling OpenGL application with CMake

Packages don't have to be required because many projects don't require every single library they can use. For example, not requiring libpng just means if it's not on the system then your project can't open pngs. Andrea Tagliasacchi wrote: This is a bit odd to me. Why would not everything be

[CMake] Problems with parsing and CMAKE_MODULE_PATH

I am running cmake 2.6.3 on vista32 1. Is there any way to add a path for cmake to permanently look for modules/packages in? I am writing a package, which I have in SVN, and I really don't want to copy it back and forth to the cmake folder or I will get out of whack. And when I set the

[CMake] Problems with target_link_libraries picking up both sets of libraries

I am using cmake 2.6.3 on vista. I am having trouble with the target_link_libraries appearing to not picking up the right libraries in visual studio and nmake when I use debug and optimizedIt appears to add both sets of libraries in many cases. I haven't been able to detect clear patterns with

[CMake] Installed DMG, but getting problems...

I installed cmake-2.6.3-Darwin-universal via the DMG on my Mac, but I'm getting the following problems.  I did not see addressing these issues called out in the install instructions for the DMG, so can some one point me in the proper direction? Thank you for your help.

[CMake] problem with add_custom_command / add_custom_target in different directories

I'm trying to come up with a way to have a custom target defined in the top-level directory execute a collection of custom commands previously defined in subdirectories throughout the code (to untar many tarballs). Unfortunately, the approach I'm trying isn't working. When I invoke

Re: [CMake] debug, optimized, and custom

Am Mittwoch 25 Februar 2009 05:26:57 schrieb Jesse Perla: If I add on my own value to CMAKE_CONFIGURATION_TYPES so that I can have a separate build type in visual studio, etc. with compile time choice of build types, then how do I change the target_link_libraries to for this new build type?

Re: [CMake] Installed DMG, but getting problems...

It looks like you don't have Xcode tools installed. It is on the Mac OS X install DVD and you may also download it from Apple. David From: cmake-boun...@cmake.org [cmake-boun...@cmake.org] On Behalf Of Jason Rupert [jasonkrup...@yahoo.com] Sent:

Re: [CMake] Installed DMG, but getting problems...

On 25. Feb, 2009, at 5:35, Jason Rupert wrote: I installed cmake-2.6.3-Darwin-universal via the DMG on my Mac, but I'm getting the following problems. I did not see addressing these issues called out in the install instructions for the DMG, so can some one point me in the proper