Re: [CMake] Enabling C++0x support

On Wed, 4 May 2011 23:58:56 +0200, Guido Winkelmann said: >Is there a way to specify, in a cross-platform compatible manner, that a >given >C++ source file (or a target or an entire project) requires support for C >++ 0x, >so that whatever compiler flags would be necessary for that for the curre

[CMake] Enabling C++0x support

Hi, Is there a way to specify, in a cross-platform compatible manner, that a given C++ source file (or a target or an entire project) requires support for C++ 0x, so that whatever compiler flags would be necessary for that for the current platform and compiler will be set? For example, when us

Re: [CMake] cmake not found

2011/5/4 Bill Hoffman : > On 5/4/2011 1:32 PM, David Henderson wrote: >> >> I was abbreviating for conciseness on the path. I've tried running this >> in an MSYS cmd window and get the same error. >> > > Seriously, I think you have a cygwin make.exe on your system.  I don't think > msys is capable

Re: [CMake] cmake not found

On 5/4/2011 1:32 PM, David Henderson wrote: I was abbreviating for conciseness on the path. I've tried running this in an MSYS cmd window and get the same error. Seriously, I think you have a cygwin make.exe on your system. I don't think msys is capable of producing this as output: /cygdrive

Re: [CMake] build dependency graph?

On Tuesday 03 May 2011, Anders Wallin wrote: > Hi all, > I'm trying this to generate a graphviz dependency graph > http://www.cmake.org/Wiki/CMake:For_CMake_Hackers > > however I have most of my code in sub-directories with their own > CMakeLists.txt files which are included from the root director

Re: [CMake] Code::Blocks Source Tree

On Tuesday 03 May 2011, Jesse Werner wrote: > When I build a Code::Blocks project my source tree in the Management window > starts from the home folder. Is there a way to change this? I would like it > to be relative to my project folder. I have done some searching for the > solution and someone sa

Re: [CMake] Testing and DLLs

I forgot to reply to all. The gist is that I did override the output directories in some sub-modules. I.e. setting CMAKE_*_OUTPUT_DIRECTORY is really all I need. - Hauke On Wed, May 4, 2011 at 6:26 PM, Michael Jackson wrote: > Are you talking about the actual library/DLL that you are creating o

Re: [CMake] cmake not found

I was abbreviating for conciseness on the path. I've tried running this in an MSYS cmd window and get the same error. I've spent the morning trying to dump out as many environment variables that may be related as possible. This is really frustrating as the build just works on Linux... Sen

Re: [CMake] Testing and DLLs

On Wed, May 4, 2011 at 12:25 PM, Michael Jackson wrote: > Funny, I did the same thing using pure CMake code because I couldn't figure > out batch files. > BTW, I started from your example of your macro to create my macro. Thanks. John ___ Powered by w

Re: [CMake] Testing and DLLs

Are you talking about the actual library/DLL that you are creating or some 3rd party library that your built library depends on? If you do this: # -- Setup output Directories - SET (CMAKE_LIBRARY_OUTPUT_DIRECTORY ${PROJECT_BINARY_DIR}/Bin CACHE PATH "Single D

Re: [CMake] Testing and DLLs

Funny, I did the same thing using pure CMake code because I couldn't figure out batch files. # #-- Copy all the dependent DLLs into the current build directory so that the test #-- can run. MACRO (CMP_COPY_DEPENDENT_LIBRARIES

Re: [CMake] Testing and DLLs

> I am curious whether there is a common way of dealing with unit tests > when the actual project to be tested is a DLL? The issue I am facing > is a common Windows issue where the required DLL is not found in the > path. > > I tried to put all binaries in the same directory by modifying > CMAKE_*_

[CMake] Testing and DLLs

Hi, I am curious whether there is a common way of dealing with unit tests when the actual project to be tested is a DLL? The issue I am facing is a common Windows issue where the required DLL is not found in the path. I tried to put all binaries in the same directory by modifying CMAKE_*_OUTPUT_D

Re: [CMake] adding a 'make altinstall' to cmake?

On 05/04/2011 11:51 AM, Rolf Eike Beer wrote: >> hi michael, >> >> thanks for the tip, this makes a lot of sense. unfortunately, the >> following does not work: >> >> add_custom_command(TARGET libopenrave POST_BUILD COMMAND >> ${CMAKE_COMMAND} -E create_symlink $ >> $ ) >> >> doing a grep on buil

[CMake] ProjectConfig.cmake files with both dynamic and static libraries?

Hi, I've been working on adding Config.cmake support to my CMake based projects, and just had a quick question regarding 'best practice' in writing these when the project builds both dynamic and (optionally) static libraries, with clients of the project wishing to choose one or the other. Thanks

Re: [CMake] adding a 'make altinstall' to cmake?

> hi michael, > > thanks for the tip, this makes a lot of sense. unfortunately, the > following does not work: > > add_custom_command(TARGET libopenrave POST_BUILD COMMAND > ${CMAKE_COMMAND} -E create_symlink $ > $ ) > > doing a grep on build.make, i see the following: > > /usr/bin/cmake -E creat

[CMake] install(EXPORT) and Mac OS X frameworks

Hi all How would I instruct install(EXPORT) to install the file into my Mac OS X framework elegantly? For source files I can do so using the MACOSX_PACKAGE_LOCATION property, but it would be nice if I didn't have to guess/hard-code the directory inside the framework for the exports-file too. Anybo

Re: [CMake] adding a 'make altinstall' to cmake?

hi michael, thanks for the tip, this makes a lot of sense. unfortunately, the following does not work: add_custom_command(TARGET libopenrave POST_BUILD COMMAND ${CMAKE_COMMAND} -E create_symlink $ $ ) doing a grep on build.make, i see the following: /usr/bin/cmake -E create_symlink $ $ accor