Re: [CMake] Adding Generated Header to VS Project

2007-06-19 Thread Mike Jackson
INCLUDE_DIRECTORIES("${CMAKE_CURRENT_BINARY_DIR}") does the trick. Sorry for not getting back to the list sooner. Problem solved. -- Mike Jackson Senior Research Engineer Innovative Management & Technology Services On Jun 19, 2007, at 6:25 PM, Jack Kelly wrote: Brandon Van Every wrote:

Re: [CMake] Adding Generated Header to VS Project

2007-06-19 Thread Jack Kelly
Brandon Van Every wrote: > On 6/19/07, Mike Jackson <[EMAIL PROTECTED]> wrote: >> I have the following as part of my CMakeLists.txt file: >> >> CONFIGURE_FILE(${MXADataModel_SOURCE_DIR}/src/Headers/MXAConfiguration.h.in >>${PROJECT_BINARY_DIR}/MXAConfiguration.h @ONLY IMMEDIATE)

Re: [CMake] FILE command in make_custom_target

2007-06-19 Thread Brandon Van Every
On 6/19/07, Bill Hoffman <[EMAIL PROTECTED]> wrote: Philippe Fremy wrote: > > It is ironic that a running cmake instance, that supports platform > agnostic directory creation, is not able to do that inside a rule and > has to fallback an calling a second cmake instance for that. > > Actually, whe

Re: [CMake] FILE command in make_custom_target

2007-06-19 Thread Brandon Van Every
On 6/19/07, Philippe Fremy <[EMAIL PROTECTED]> wrote: It is ironic that a running cmake instance, that supports platform agnostic directory creation, is not able to do that inside a rule and has to fallback an calling a second cmake instance for that. I agree. However, I've come to accept th

Re: [CMake] Adding Generated Header to VS Project

2007-06-19 Thread Brandon Van Every
On 6/19/07, Mike Jackson <[EMAIL PROTECTED]> wrote: I have the following as part of my CMakeLists.txt file: CONFIGURE_FILE(${MXADataModel_SOURCE_DIR}/src/Headers/MXAConfiguration.h.in ${PROJECT_BINARY_DIR}/MXAConfiguration.h @ONLY IMMEDIATE) INCLUDE_DIRECTORIES("${PROJECT_BINARY_D

Re: [CMake] how to use a cross linker

2007-06-19 Thread kitts
On Monday 18 Jun 2007 6:23:46 pm you wrote: > > Yes. This was my first project with cmake and i dint know the ways in > > which i had to use it. I know i dint want to place any files into the > > cmake installation as that would be hard to maintain and distribute > > unless supported upstream. > >

[CMake] Adding Generated Header to VS Project

2007-06-19 Thread Mike Jackson
I have the following as part of my CMakeLists.txt file: CONFIGURE_FILE(${MXADataModel_SOURCE_DIR}/src/Headers/MXAConfiguration.h.in ${PROJECT_BINARY_DIR}/MXAConfiguration.h @ONLY IMMEDIATE) INCLUDE_DIRECTORIES("${PROJECT_BINARY_DIR}") And in a source file I then have: #include A

[CMake] resetting /VERSION and /STACK linker options within visual studio

2007-06-19 Thread Jon W
I'm in the process of porting existing visual studio projects to cmake. As such, I want to duplicate the compiler and linker options of the existing project files. I'm using 2.4.7 RC10. The first question is, how do I get rid of the /VERSION:0.0 linker flag? This flag seems to be generated by

Re: [CMake] FILE command in make_custom_target

2007-06-19 Thread Bill Hoffman
Philippe Fremy wrote: It is ironic that a running cmake instance, that supports platform agnostic directory creation, is not able to do that inside a rule and has to fallback an calling a second cmake instance for that. Actually, when a custom command is run, there is no running cmake insta

Re: [CMake] FILE command in make_custom_target

2007-06-19 Thread Philippe Fremy
Brandon Van Every wrote: > On 6/17/07, Philippe Fremy <[EMAIL PROTECTED]> wrote: >> >> Hi, >> >> I want a directory to be built when a custom target is executed. >> >> I tried something like this: >> >> add_custom_target( >> doc_libyzis >> COMMAND FIL

[CMake] CMake Packaging (CMAKE_EXPORT_BUILD_SETTINGS)

2007-06-19 Thread Mathieu Malaterre
Hello, I was trying to find documentation on CMAKE_IMPORT_BUILD_SETTINGS / CMAKE_EXPORT_BUILD_SETTINGS. Since I could not find a lot, I decided to start a wiki page: http://cmake.org/Wiki/CMake_Package This is simply a copy paste from a post from Brad King. What is still missing is : 1. Hand