[CMake] CMake Tools for Visual Studio 1.0 RC2 Available

I've made available CMake Tools for Visual Studio 1.0 RC2, which incorporates several bug fixes and enhancements since RC1. It can be downloaded from http://cmaketools.codeplex.com. Enjoy! David Golub -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kit

[CMake] Ninja and .o targets dependencies on dynamic libraries

The ninja targets generated by cmake for our project have the .o targets used to build libraries that have order-only dependencies on the dynamic libraries to which the resulting library will be linked. That is - libfoo.so is built from foo.o and libbar.so and - foo.o has an order-only dependency o

Re: [CMake] Add a manifest file to the created jar

On 2013-06-17 12:25, Matthew Woehlke wrote: On 2013-06-17 09:59, paul.chav...@fnac.net wrote: Following this thread¹ and bug², i would like to submit a patch that allow to specify a Manifest.txt when creating a jar. ¹ http://www.cmake.org/pipermail/cmake/2011-December/048015.html ² http://publi

Re: [CMake] Add a manifest file to the created jar

On 2013-06-17 09:59, paul.chav...@fnac.net wrote: Following this thread¹ and bug², i would like to submit a patch that allow to specify a Manifest.txt when creating a jar. ¹ http://www.cmake.org/pipermail/cmake/2011-December/048015.html ² http://public.kitware.com/Bug/view.php?id=12886 Could yo

[CMake] Add a manifest file to the created jar

Hi Following this thread ( http://www.cmake.org/pipermail/cmake/2011-December/048015.html ) and bug ( http://public.kitware.com/Bug/view.php?id=12886 ), i would like to submit a patch that allow to specify a Manifest.txt when creating a jar. Could you review it please ? Regards. Paul. From

[CMake] CPACK + NSIS: Can I install some files in a seperate (non-system) file tree or change directory permissions?

I have another problem with my CPack installer for windows. I want to install a couple of test input files for my program. However, I need my program to be able to write into the same directory as that of the input files. Since this directory is in a system directory (Program Files (x86)), on

[CMake] How to define a compiler flags that do not appear in linker command line

Hi, I'm using CMake (2.8.10.1) to cross-compile from OS X and Linux x86_64 hosts to ARM EABI platform running eCos. I'm looking for a way (and if possible, a clean one ;-)) to define C compiler flags that are not propagated to the final link stage. My current CMake files use: SET (CMAKE_SYSTEM_