Re: [cmake-developers] Request for Comments: Will implementing an interactive CMake debugger be welcome?

2013-01-08 Thread Shlomi Fish
Hi Matt, On Mon, 7 Jan 2013 17:06:11 -0700 Matt McCormick matt.mccorm...@kitware.com wrote: Hi Shlomi, I also think this would be a great feature. I started on an implementation here: https://github.com/thewtex/cmakedbg but I have not had time to follow it through. The user

Re: [cmake-developers] FreeGLUT Module

2013-01-08 Thread Rolf Eike Beer
Am , schrieb Янчарук Александр: Hi! In the attachment module for FreeGLUT library. Hope this will be usefull. Tested on Debian squeeze with freeglut3-dev package. Module was originally made from GLUT-module. It looks very similar to the GLUT module indeed. I wonder why one can't just add

Re: [cmake-developers] [SOLVED]DESTDIR does not work correctly with install(FILES ... signature

2013-01-08 Thread Eric Noulard
2013/1/8 Alan W. Irwin ir...@beluga.phys.uvic.ca: On 2013-01-08 10:47+0100 Eric Noulard wrote: 2013/1/8 Alan W. Irwin ir...@beluga.phys.uvic.ca: The rule should be simple as: You need to escape one time less than the number of cmake run occuring through the workflow path. In your case

Re: [cmake-developers] FreeGLUT Module

2013-01-08 Thread Rolf Eike Beer
Янчарук Александр wrote: Adding the freeglut library to GLUT module would be solution for systems where installed glut lib. What if some one decide install latest FreeGLUT lib from source? In your case for succesful use of FreeGLUT i need install additional packages (glutg3 glutg3-dev in

Re: [cmake-developers] Interface includes and defines plumbing

2013-01-08 Thread Brad King
On 01/07/2013 06:54 PM, Stephen Kelly wrote: It's not clear how to add the commands without bootstrapping them. In my branch, the BootstrapTest fails: Add the commands to cmCommands.cxx rather than cmBootstrapCommands.cxx and do not list them as sources in CMakeLists.txt. -Brad --

Re: [cmake-developers] Interface includes and defines plumbing

2013-01-08 Thread Stephen Kelly
Brad King wrote: On 01/07/2013 06:54 PM, Stephen Kelly wrote: It's not clear how to add the commands without bootstrapping them. In my branch, the BootstrapTest fails: Add the commands to cmCommands.cxx rather than cmBootstrapCommands.cxx and do not list them as sources in

[cmake-developers] [CMake 0013840]: Allow generator expressions anywhere

2013-01-08 Thread Mantis Bug Tracker
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=13840 == Reported By:raspy Assigned To:

[cmake-developers] CMake build error on Haiku

2013-01-08 Thread Rolf Eike Beer
Recent CMake versions fail to build at Haiku: [ 0%] Building C object Utilities/KWIML/test/CMakeFiles/cmIML_test.dir/test_ABI_C.c.o In file included from /boot/home/cmake/Utilities/KWIML/test/test_ABI_C.c:13: /boot/home/build/cmake/Utilities/cmIML/ABI.h:261: #error Existence of 'long long'

Re: [cmake-developers] CMake build error on Haiku

2013-01-08 Thread Rolf Eike Beer
Bill Hoffman wrote: On 1/8/2013 1:43 PM, Rolf Eike Beer wrote: Recent CMake versions fail to build at Haiku: Can you or someone run a dashboard for this? Without one we are doomed to have this fail again and again. I can't, and I don't really care about Haiku. I was just testing out some

Re: [cmake-developers] CMake build error on Haiku

2013-01-08 Thread Brad King
On 01/08/2013 01:43 PM, Rolf Eike Beer wrote: I have not submitted it to the next branch because I assume this is another Kitware magic upstream tree: It is. diff --git a/Utilities/KWIML/ABI.h.in b/Utilities/KWIML/ABI.h.in index 7f4772a..a336a80 100644 --- a/Utilities/KWIML/ABI.h.in +++

Re: [cmake-developers] CMake build error on Haiku

2013-01-08 Thread Rolf Eike Beer
Am , schrieb Brad King: On 01/08/2013 01:43 PM, Rolf Eike Beer wrote: I have not submitted it to the next branch because I assume this is another Kitware magic upstream tree: It is. diff --git a/Utilities/KWIML/ABI.h.in b/Utilities/KWIML/ABI.h.in index 7f4772a..a336a80 100644 ---

Re: [cmake-developers] CMake build error on Haiku

2013-01-08 Thread Brad King
On 01/08/2013 03:08 PM, Rolf Eike Beer wrote: Am , schrieb Brad King: +# elif defined(__GNUC__) __GNUC__ == 2 +# define @KWIML@_ABI_SIZEOF_LONG_LONG 8 I don't know when this SIZEOF_LONG_LONG was introduced. If it is present it is used before anyway. I just fear there are early 3.x

Re: [cmake-developers] CMake build error on Haiku

2013-01-08 Thread Brad King
On 01/08/2013 03:28 PM, Brad King wrote: On 01/08/2013 03:08 PM, Rolf Eike Beer wrote: Am , schrieb Brad King: +# elif defined(__GNUC__) __GNUC__ == 2 +# define @KWIML@_ABI_SIZEOF_LONG_LONG 8 I don't know when this SIZEOF_LONG_LONG was introduced. If it is present it is used before

Re: [CMake] [cmake-developers] FreeGLUT Module

2013-01-08 Thread Rolf Eike Beer
Am , schrieb Янчарук Александр: Hi! In the attachment module for FreeGLUT library. Hope this will be usefull. Tested on Debian squeeze with freeglut3-dev package. Module was originally made from GLUT-module. It looks very similar to the GLUT module indeed. I wonder why one can't just add

[CMake] something like atexit

2013-01-08 Thread Tomasz Majchrowski
Dear CMake Community I'm maintaining set of macros which is used by group of developers in their own set of CMakeLists.txt In order to include CPack and also do some other post check/configuration I would need to have function like atexit, so I will be sure that it's the last call before cmake

[CMake] Dealing with custom command outputs when using clean

2013-01-08 Thread Willy Lambert
Hi all, When I build my project I use the EXECUTABLE_OUTPUT_PATH to produce my binaries. As I also want to split the binaries between the stripped stuff and the debug stuff (so basically I have a exe and exe.debug). This is done with objcopy, so I use a custom command : set( EXEC

Re: [CMake] Dealing with custom command outputs when using clean

2013-01-08 Thread Petr Kmoch
Hi Willy. I believe the property ADDITIONAL_MAKE_CLEAN_FILES should be set on the directory which *creates* the file, not the one which contains it on disk. Petr On Tue, Jan 8, 2013 at 10:42 AM, Willy Lambert lambert.wi...@gmail.comwrote: Hi all, When I build my project I use the

Re: [CMake] Dealing with custom command outputs when using clean

2013-01-08 Thread Willy Lambert
Dear Petr, Thanks for this instant support :D The correct line was : set_directory_properties(PROPERTY ADDITIONAL_MAKE_CLEAN_FILES ${EXECUTABLE_OUTPUT_PATH}/${EXEC_NAME}.debug) So you are rigth, the directory is the current one (in this case) and the target file must be surround by the

[CMake] LINK_PRIVATE and install(EXPORT behavior

2013-01-08 Thread Gregoire Aujay
Hello, I am using cmake 2.8.10.2 on windows. I want a library A to link to a 3rdParty library B. I thought that using LINK_PRIVATE version of the target_link_libraries function should avoid B to be in the link interface of A. But if I export A, B's full path is in

[CMake] random BAD_COMMAND error on ctest

2013-01-08 Thread BILODEAU Andre
I just began to make ctest replace autotools for the program I develop, but I still have some problems while running ctest. Computer: Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz RAM 3,37 GO System: Microsoft Windows XP Version 2002 Service Pack 3 Environment: Cygwin 1.7.17(0.262/5/3) cmake

Re: [CMake] random BAD_COMMAND error on ctest

2013-01-08 Thread Eric Noulard
2013/1/8 BILODEAU Andre andre.bilod...@safran-engineering.com: I just began to make ctest replace autotools for the program I develop, but I still have some problems while running ctest. Computer: Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz RAM 3,37 GO System: Microsoft Windows XP

Re: [CMake] random BAD_COMMAND error on ctest

2013-01-08 Thread Eric Noulard
2013/1/8 BILODEAU Andre andre.bilod...@safran-engineering.com: Thank you for your fast answer... I have made more testing, in order to answer more questions: 1- With ctest -VV, the timeout is 9.99e+06, which seems comfortable. 2- With set_tests_properties, I set the timeout to 100. No

Re: [CMake] random BAD_COMMAND error on ctest

2013-01-08 Thread Allen D Byrne
, but with no interesting answer. Is this king of behavior already known ? Does that correspond to a bug ? Is there a known workaround ? andre -- next part -- An HTML attachment was scrubbed... URL: http://www.cmake.org/pipermail/cmake/attachments/20130108/64786bbe/attachm

[CMake] Fwd: random BAD_COMMAND error on ctest

2013-01-08 Thread Eric Noulard
FWD to mailing list for other. Andre beware not to drop the CMake ML address -- Forwarded message -- From: BILODEAU Andre andre.bilod...@safran-engineering.com Date: 2013/1/8 Subject: RE: [CMake] random BAD_COMMAND error on ctest To: Eric Noulard eric.noul...@gmail.com I have

Re: [CMake] something like atexit

2013-01-08 Thread Alexander Neundorf
On Tuesday 08 January 2013, Tomasz Majchrowski wrote: Dear CMake Community I'm maintaining set of macros which is used by group of developers in their own set of CMakeLists.txt In order to include CPack and also do some other post check/configuration I would need to have function like

Re: [CMake] something like atexit

2013-01-08 Thread Eric Noulard
2013/1/8 Alexander Neundorf a.neundorf-w...@gmx.net: On Tuesday 08 January 2013, Tomasz Majchrowski wrote: Dear CMake Community I'm maintaining set of macros which is used by group of developers in their own set of CMakeLists.txt In order to include CPack What's the problem here? You want

Re: [CMake] LINK_PRIVATE and install(EXPORT behavior

2013-01-08 Thread Stephen Kelly
Gregoire Aujay wrote: Hello, I am using cmake 2.8.10.2 on windows. I want a library A to link to a 3rdParty library B. I thought that using LINK_PRIVATE version of the target_link_libraries function should avoid B to be in the link interface of A. But if I export A, B's full path is in

[CMake] Building a library for both C and C++

2013-01-08 Thread kgardenia42
Hi list, I am trying to write a CMakeLists.txt where the same source files are compiled separately to both a C library and a C++ library. So, lets say I have foo.c, bar.c and baz.c and I would like to build mylib.a and mylib++.a My intuition is to use one CMakefile and add multiple targets for

Re: [CMake] random BAD_COMMAND error on ctest

2013-01-08 Thread Eric Noulard
Andre please do not drop the ML address. 2013/1/9 BILODEAU Andre andre.bilod...@safran-engineering.com: New test: I just replaced my test driver by a simple stub, which is run for each of the tests from test_01 to test_17: #!/bin/ksh exit 0 All the tests run without error. That seems

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1468-gf7837b8

2013-01-08 Thread Stephen Kelly
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 f7837b8ac4e14fa60bb2ef614c01c66620fe50ac (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1471-g5fbb5ef

2013-01-08 Thread Brad King
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 5fbb5eff943d622219d806ddc447744b087cef20 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1480-g2d80aa8

2013-01-08 Thread Brad King
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 2d80aa8046360f25da5652d139a98495101617be (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1483-g1ef1045

2013-01-08 Thread Stephen Kelly
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 1ef104503e647998c0f2a8365f430cc0160db235 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1485-gc16df1c

2013-01-08 Thread Brad King
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 c16df1c3e64d3e1b3116aaabf35ed81ccfc759b1 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-397-gaf770bc

2013-01-08 Thread Brad King
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, master has been updated via af770bc27e7870ef2e3796163ff610773cb51a38 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-401-gbc414ae

2013-01-08 Thread Brad King
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, master has been updated via bc414aebaf80cf7a5c67e79e1a5d1f4417164263 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-403-g6095e9f

2013-01-08 Thread Brad King
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, master has been updated via 6095e9fda68810a98be23750b7a0765967d12679 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-406-ge41d495

2013-01-08 Thread Brad King
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, master has been updated via e41d4951b366cd34a1fd5129deb7e61e906db6ec (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-409-ga9f1bf4

2013-01-08 Thread Brad King
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, master has been updated via a9f1bf438054227e989ad1706b785b978e18455c (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1494-g636f4f4

2013-01-08 Thread Stephen Kelly
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 636f4f4325d21ed078b8fac0c57c24ac58a69271 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1508-gd118a42

2013-01-08 Thread Brad King
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 d118a423d728e2e0adddb1d0cdad3fccbb9f8c4f (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-410-g30c02f1

2013-01-08 Thread Kitware Robot
Stamp diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 528fa13..d1b2097 100644 --- a/Source/CMakeVersion.cmake +++ b/Source/CMakeVersion.cmake @@ -2,5 +2,5 @@ set(CMake_VERSION_MAJOR 2) set(CMake_VERSION_MINOR 8) set(CMake_VERSION_PATCH 10) -set(CMake_VERSION_TWEAK 20130108

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1510-ge49d857

2013-01-08 Thread Stephen Kelly
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 e49d857e7086bbd3b3d600cd02d5c00d3a02f231 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1512-g50e4e0f

2013-01-08 Thread Stephen Kelly
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 50e4e0f12c22dc88dba550ba96a46c1ca1d634f0 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1514-gfba9a5a

2013-01-08 Thread Stephen Kelly
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 fba9a5a6a2243583fa9477bd61177c226eea1fdd (commit) via