[CMake] Getting the Generator during CMAKE

I need to have my CMakeLists file do different things depending on the Generator that is being used. Mostly passing on that version information to a build of a 3rd party library. Is there a way to get that information during the CMake run? -Neal ___

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

Re: [CMake] Unix make files and CMAKE_EXE_LINKER_FLAGS_RELEASE

. This seems much simpler, because it allows for the combination of the Linker Flags which is nice for avoiding repetition in the flags. -Neal On Tue, Feb 24, 2009 at 3:54 PM, Philip Lowman phi...@yhbt.com wrote: On Tue, Feb 24, 2009 at 6:45 PM, Neal Meyer nme...@dottedzebra.comwrote: Philip

Re: [CMake] Unix Makefiles/XCode not linking properly on Mac

directory, but to no avail. -Neal On Fri, Nov 14, 2008 at 5:16 AM, Michael Jackson [EMAIL PROTECTED] wrote: On Nov 13, 2008, at 7:59 PM, Neal Meyer wrote: I have a project that I have been working on for a while using the Visual Studio generator in Windows, and I am now attempting to build

Re: [CMake] Unix Makefiles/XCode not linking properly on Mac

not need an add_dependencies call after the add_executable, you need a target_link_libraries to tell the exe to link in the library... HTH, David On Fri, Nov 14, 2008 at 1:23 PM, Neal Meyer [EMAIL PROTECTED]wrote: I built an extremely simple project. Contains main.cpp, and then a library

[CMake] Unix Makefiles/XCode not linking properly on Mac

I have a project that I have been working on for a while using the Visual Studio generator in Windows, and I am now attempting to build in on Mac. Right now it's very early and I'm having problems building any of the executables using the Unix Makefile generation or the XCode generator. It's

Re: [CMake] Eclipse CDT and CMake

PROTECTED] Content-Type: text/plain; charset=ISO-8859-1 2008/11/7 Michael Jackson [EMAIL PROTECTED]: On Nov 6, 2008, at 7:26 PM, Neal Meyer wrote: I'm on a Mac and I was wondering if there are any plans to support full CDT projects from CMake? -Neal I thought there was a CDT generator

Re: [CMake] Eclipse CDT and CMake

an add_subdirectory in the root CMakeLists.txt file, but on my Mac project I'm just getting a single linked resource for the root of the entire source tree. Is that expected? Both are using out of source build directories. -Neal On Friday 07 November 2008, Neal Meyer wrote: I've tried the existing

Re: [CMake] Eclipse CDT and CMake

always be left in the eclipse project then if I have a project() call there? -Neal On Fri, Nov 7, 2008 at 12:31 PM, Miguel A. Figueroa-Villanueva [EMAIL PROTECTED] wrote: On Fri, Nov 7, 2008 at 4:11 PM, Neal Meyer wrote: On Friday 07 November 2008, Neal Meyer wrote: I've tried the existing

[CMake] Eclipse CDT and CMake

I'm on a Mac and I was wondering if there are any plans to support full CDT projects from CMake? -Neal ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake

[CMake] XCode 3.0

Are there any plans or WIP for support XCode 3.0-3.1 projects? To support the build targets in parallel option. Also is there an easy way to set the GCC version that is used by the XCode project? so the projects will use the latest version of GCC rather then 4.0. -Neal

[CMake] Get the drive from a path

On windows I need a way to get a drive letter from a path. Does anybody have any tricks for doing this? -Neal ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] using SOURCE_GROUP

You just need to use the other slash SOURCE_GROUP( source\\subgroup FILES ${SOURCES} ) -Neal On 10/19/07, Mark Wyszomierski [EMAIL PROTECTED] wrote: Hi, Is it possible to create sub folders in the source tree for vc++ makes? I'm trying something like: IF (WIN32) SOURCE_GROUP(Source

[CMake] Removing CMakeLists from Visual Studio project files or excluding from the build

Is there a way that the CMakeLists.txt files can be excluded from building in Visual Studio, or removed from the generated projects? -Neal ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake

[CMake] Visual Studio 2005 ADD_CUSTOM_TARGET

Here is what I have in my cmake file ADD_CUSTOM_TARGET( my_target ALL COMMAND build.bat DEPENDS ${SOURCES} ) In Visual Studio I'm expecting to get a Utility Project, the the build command set to build.bat, but the

Re: [CMake] Dependencies for EXEC_PROGRAM

of the CUSTOM_COMMAND.. -Neal On 10/1/07, Alan W. Irwin [EMAIL PROTECTED] wrote: On 2007-10-01 14:15-0700 Neal Meyer wrote: I've got a static library that contains generated code, today this is done in a make file so I can check the dependencies before the PERL script is called again during the build

[CMake] Dependencies for EXEC_PROGRAM

I've got a static library that contains generated code, today this is done in a make file so I can check the dependencies before the PERL script is called again during the build process. I'm adding a CustomBuildCommand to the project, so the dependecies are properly checked in my vcproj files.

Re: [CMake] Project Grouping in a solution

Richard, This project organization is much better, Kudos. However, most of our directories include only a single project file so there seems to be a lot of redundant folders in this type of layout, so maybe a little additional feature that if there is only a single project in the directory don't

[CMake] Visual Studio 8 and warning levels

I'm having some trouble getting a clean way to set the warning level in my projects with Visual Studio 2005. When I try this SET(CMAKE_C_WARNING_LEVEL 4) SET(CMAKE_CXX_WARNING_LEVEL 4) It seems to be ignored because the project files still have the warning level set to 3. I only want to turn up

[CMake] Project Grouping in a solution

Is there a way to group projects in a solution? Something like this would be handy CMakeProject -- ALL_BUILD -- ZERO_CHECK etc lib -- lib1 -- lib2 Possibly something that follows the file system setup. -Neal ___ CMake mailing

[CMake] Passing lists to macros

I've got the following in my CMakeLists.txt SET( L1 *.h *.hpp *.cpp *.c ) MESSAGE( STATUS L1 = ${L1} ) macro( test L2 ) MESSAGE( STATUS L2 = ${L2} ) FOREACH( L ${L2} ) MESSAGE( STATUS L = ${L} ) SET( L_LIST ${L_LIST} stuff/${L} ) ENDFOREACH( L ) MESSAGE( STATUS L_LIST = ${L_LIST} )