Re: [cmake-developers] Perforce Patch for CTest

2013-10-24 Thread Brad King
On 10/24/2013 03:11 AM, Rolf Eike Beer wrote: CMake/Source/CTest/cmCTestP4.cxx: In member function ‘virtual void cmCTestP4::LoadRevisions()’: CMake/Source/CTest/cmCTestP4.cxx:469:32: warning: conversion to ‘int’ from ‘std::vectorstd::basic_stringchar ::size_type {aka long unsigned int}’

[cmake-developers] ExternalProject update target dependencies

2013-10-24 Thread Daniele E. Domenichelli
Hello all, I have another issue with ExternalProject. If I add 2 external projects (A and B), with B DEPENDS=A, and STEP_TARGETS=update, I expect to be able to update B without updating, building and installing A, since just updating the code is obviously not dependent. I tried to look at

Re: [cmake-developers] Perforce Patch for CTest

2013-10-24 Thread Brad King
On 10/24/2013 08:17 AM, Brad King wrote: Also std::size_t does not work on VS 6. Both fixed: Also a couple fixes to the test: CTest.UpdateP4: Fix test when p4 client is not in PATH http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ee51ec64eb CTest.UpdateP4: Run test in directory with space

[cmake-developers] Testing CMake

2013-10-24 Thread Nils Gladitz
Hello, I've been wondering about the test setup in Tests/CMakeLists.txt. Is CMAKE_CTEST_COMMAND in that context the newly build ctest or the old one that performed the build? Does CMAKE_CTEST_COMMAND when invoked with --build-and-test perhaps run that build and test with the new binaries?

Re: [cmake-developers] CTest: Request review of topic ctest-fix-run-serial

2013-10-24 Thread Nils Gladitz
Thanks Bill, I think I can probably fix that by replacing the insert with a manual loop. SSH access is being blocked here so I probably wont get to fix it before I get home but looks like the client only builds nightly anyway :) Nils On 10/24/2013 03:40 PM, Bill Hoffman wrote: On

Re: [cmake-developers] C++11 and target_compiler_feature proposal

2013-10-24 Thread Stephen Kelly
Brad King wrote: On 10/23/2013 05:59 PM, Stephen Kelly wrote: CMAKE_CXX_COMPILER is always set to the proper full path these days, even in the IDE generators, so I wonder if we could actually run it against the header file to detect the features available for the current compiler instead of

[cmake-developers] Major.Minor version install directories

2013-10-24 Thread Stephen Kelly
Hello, My install prefix currently looks something like this: l -1 /home/stephen/dev/prefix/qtbase/kde/doc/ cmake-2.8/ cmake-2.8.12.20131023-g07324-dirty/ cmake-2.8.12.20131023-g10e02-dirty/ cmake-2.8.12.20131023-g1bfc2/ cmake-2.8.12.20131023-g3dec3/ cmake-2.8.12.20131023-g5a601/

Re: [cmake-developers] Review request: Qt-auto-generators

2013-10-24 Thread Alexander Neundorf
On Thursday 24 October 2013, Stephen Kelly wrote: Hi, I've pushed the Qt-auto-generators topic to stage. This topic was discussed here: http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/7936 I have tested it with ports of KDE Frameworks and GammaRay to use the features.

Re: [cmake-developers] Review request: Qt-auto-generators

2013-10-24 Thread Stephen Kelly
Alexander Neundorf wrote: On Thursday 24 October 2013, Stephen Kelly wrote: Hi, I've pushed the Qt-auto-generators topic to stage. This topic was discussed here: http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/7936 I have tested it with ports of KDE Frameworks and

Re: [cmake-developers] Perforce Patch for CTest

2013-10-24 Thread Brad King
On 10/24/2013 03:57 PM, Pedro Navarro wrote: That's right, p4 usually doesn't create a .p4 file I think it is fine for the test to not place .p4 files since that is representative of real use cases. Ideally each VCS implementation could have a way to tell CTest if a directory it's under that