[CMake] install TARGETS given unknown argument "EXPORT". with cmake 2.8.9

2014-02-12 Thread david . hagood
I am trying to set up component registration as per http://www.cmake.org/Wiki/CMake/Tutorials/Packaging but when I run Cmake I get the error install TARGETS given unknown argument "EXPORT". While I've found many hits on Google with that error string, none that I have found have any resolutio

Re: [CMake] CMake + Ninja + MSVC confusion

2014-02-12 Thread Alan W. Irwin
On 2014-02-12 17:22- Dominic Walsh wrote: Hi I am trying to use the Ninja generator to compile on a Windows machine using the Visual Studio 11 compilers. From a VS11 console I run cmake (version: 2.8.11.2 ): cmake -G Ninja -DCMAKE_BUILD_TYPE=Debug -DCMAKE_SYSTEM_NAME=MSVC .. I then ru

[CMake] CMake + Ninja + MSVC confusion

2014-02-12 Thread Dominic Walsh
Hi I am trying to use the Ninja generator to compile on a Windows machine using the Visual Studio 11 compilers. >From a VS11 console I run cmake (version: 2.8.11.2 ): cmake -G Ninja -DCMAKE_BUILD_TYPE=Debug -DCMAKE_SYSTEM_NAME=MSVC .. I then run Ninja (version 1.4.0) ninja -v and all appea

Re: [CMake] Run clean before automatically re-running cmake?

2014-02-12 Thread Abe Bachrach
On Wed, Feb 12, 2014 at 8:53 AM, Matthew Woehlke < mw_tr...@users.sourceforge.net> wrote: > > What you really want is to record the "old" list of output files, re-run > CMake, then remove any files on that list that no longer have rules to > generate them. If you do a complete 'clean' you will dele

Re: [CMake] Run clean before automatically re-running cmake?

2014-02-12 Thread Matthew Woehlke
On 2014-02-12 11:35, Abe Bachrach wrote: The Makefile that cmake generates includes a rule to automatically re-run cmake if any of the input CMakelists.txt files change. Currently, if you change the name of an executable target (or library), it will leave the old file in the output location, and

[CMake] Run clean before automatically re-running cmake?

2014-02-12 Thread Abe Bachrach
Hi there, The Makefile that cmake generates includes a rule to automatically re-run cmake if any of the input CMakelists.txt files change. Is there a way to configure this rule to have it run clean first? Currently, if you change the name of an executable target (or library), it will leave the

Re: [CMake] include_directories(...) versus set_directory_properties(PROPERTIES INCLUDE_DIRECTORIES ...)

2014-02-12 Thread David Cole
>>> Should I file this as a bug in the issue tracker then? >> Sure. Especially if you have an easy way to reproduce. (Either >> reference an external, publicly available project we can "just >> build" and get it to happen, or attach a CMakeLists that >> demonstrates the issue if possible.) >> >>

Re: [CMake] include_directories(...) versus set_directory_properties(PROPERTIES INCLUDE_DIRECTORIES ...)

2014-02-12 Thread David Cole
That's just the quick brain dump version. If necessary, I can actually look at old commits, or the current code to try to refresh my memory. I think that's needed. Can you do that research into the commits and discussion? I know it's been a week now I'm still getting to this. Will re-o

Re: [CMake] cmake release and process

2014-02-12 Thread David Cole
#1. The cmake roadmap informs me that 100% of version 3.0 is complete. Any news on when this will be released?   "Soon":-) (Although, disclaimer: I'm not responsible for it anymore, so I can't be more precise than that...) #2. How does the development team decide which issues are includ

[CMake] cmake release and process

2014-02-12 Thread Lars
Hello, #1. The cmake roadmap informs me that 100% of version 3.0 is complete. Any news on when this will be released? #2. How does the development team decide which issues are included in any given release? As an example, I reported a feature request some months back (http://www.cmake.org/Bu