[cmake-developers] [CMake 0011357]: cmake bootstrap on mac jni.h error

The following issue has been SUBMITTED. == http://cmake.org/Bug/view.php?id=11357 == Reported By:Steve Pieper Assigned To:

Re: [CMake] cmake for cygwin

On Mon, 2010-10-25 at 07:57 +0200, Hendrik Sattler wrote: No. You have the same kernel under the skin and any software that has low- level parts thus needs to know that it is running on Windows, be it through the cygwin layer or not. How does it do that without the WIN32 define? With the

[CMake] Manner to manage the dependencies

Hi, This is Weiyu, a student from University of Germany. I have used CMake as the build system instead of autotool already for some projects. but I am still not sure about the way how the libraries dependencies should be handled, is there any suggestion from CMAKE group that how the

[CMake] CMake with CPack - unresolved libraries

Hello everybody. I need your help to solve the following problem. The installed version of CMake is: 2.8.0. The installed version of CPack is: 2.8.0. I am running on Ubuntu LTS 10.04. I have a CMake project. The output of the project is an executable. The executable depends on a number of

[CMake] CTest: use 'make -k' instead of 'make -i'

Hi all, I noticed that 'ctest -DExperimentalBuild' returns with an exit status 0, even if compiler errors occur. I think that is caused by the fact that 'make -i' is used. The -i|--ignore-errors option causes make to always exit with status 0. Wouldn't it make more sense to use 'make -k'

Re: [CMake] CTest: use 'make -k' instead of 'make -i'

On 25. Oct, 2010, at 16:45 , Marcel Loose wrote: Hi all, I noticed that 'ctest -DExperimentalBuild' returns with an exit status 0, even if compiler errors occur. I think that is caused by the fact that 'make -i' is used. The -i|--ignore-errors option causes make to always exit with status

Re: [CMake] CTest: use 'make -k' instead of 'make -i'

On Mon, Oct 25, 2010 at 04:54:41PM +0200, Michael Wild wrote: On 25. Oct, 2010, at 16:45 , Marcel Loose wrote: Wouldn't it make more sense to use 'make -k' instead? Some weeks ago I also wanted to propose this, but then realized one important drawback of -k: Say, you have target B

[CMake] MacOSX, Qt plugins and BundleUtilities -- not building proper bundle?

Like everyone else I started here to build my Qt app with CMake: http://www.cmake.org/Wiki/BundleUtilitiesExample Like a lot of things in CMake this involves copying a bunch of brittle CMake code into your CMakeLists.txt, and seems like it has too many moving parts and failure points, but hey, we

Re: [CMake] MacOSX, Qt plugins and BundleUtilities -- not building proper bundle?

On Oct 25, 2010, at 11:58 AM, kent williams wrote: Like everyone else I started here to build my Qt app with CMake: http://www.cmake.org/Wiki/BundleUtilitiesExample Like a lot of things in CMake this involves copying a bunch of brittle CMake code into your CMakeLists.txt, and seems like it

Re: [CMake] CMake with CPack - unresolved libraries

2010/10/25 Marcin Czenko marcin.cze...@sioux.eu: Hello everybody. I need your help to solve the following problem. The installed version of CMake is:  2.8.0. The installed version of CPack is: 2.8.0. I am running on Ubuntu LTS 10.04. I have a CMake project. The output of the project is an

[CMake] add_custom_command with PRE_BUILD and makefiles

Hi All, after moving from Visual Studio to Eclipse I realised that PRE_BUILD command does not work as expected. According to documentation: 'Note that the PRE_BUILD option is only supported on Visual Studio 7 or later. For all other generators PRE_BUILD will be treated as PRE_LINK.' I was

Re: [CMake] Manner to manage the dependencies

On Monday 25 October 2010, Weiyu Yi wrote: Hi, This is Weiyu, a student from University of Germany. I have used CMake as the build system instead of autotool already for some projects. but I am still not sure about the way how the libraries dependencies should be handled, is there any

Re: [CMake] CMake with CPack - unresolved libraries

You may try to use full RPATH: http://www.cmake.org/Wiki/CMake_RPATH_handling However I have 2 questions: 1) Is your ldd test done AFTER installing the .deb ? 2) Does the not found libraries belong to your CMake-handled project or to third party libraries? Hi Eric, Thanks for

Re: [CMake] include command

Dear all, I'm a newbie of cmake, and have some troubles in using the 'include' command. I've already include the searching path into the env veriable PATH. But each time running cmake, I always get follow error messages: CMake Error at CMakeLists.txt: xxx (include): include could not find

Re: [CMake] Status of clang support?

On 25/10/10 01:38, Mateusz Loskot wrote: On 24/10/10 23:00, Ryan Pavlik wrote: My best guess would be to check for some Clang-specific defines, similar to the platform checks. Actually, it looks like in the Git repository of CMake, there is now some Clang-specific support:

[Cmake-commits] CMake branch, next, updated. v2.8.2-1107-gaa3a813

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via aa3a813805ab22c0b64350f74f6e48d021748039 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.2-1109-g1f81929

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via 1f81929a0761b276be28d86cef2ca77a5cd25683 (commit) via