Re: [CMake] cmake 3.7.2 centos 7 :: kwsys.testSystemTools (Failed)

Adrian Sevcenco wrote: > Hi! I am trying to rebuild the f25 srpm on a centos 7 machine but after > a successful compilation i get this test error : > 99% tests passed, 1 tests failed out of 454 > > Label Time Summary: > Label1= 0.20 sec (1 test) > Label2= 0.20 sec (1 test) > > Total

[CMake] cmake 3.7.2 centos 7 :: kwsys.testSystemTools (Failed)

Hi! I am trying to rebuild the f25 srpm on a centos 7 machine but after a successful compilation i get this test error : 99% tests passed, 1 tests failed out of 454 Label Time Summary: Label1= 0.20 sec (1 test) Label2= 0.20 sec (1 test) Total Test time (real) = 257.33 sec The

Re: [CMake] cmake 3.7.2 centos 7 :: kwsys.testSystemTools (Failed)

On 02/14/2017 07:27 PM, Rolf Eike Beer wrote: Adrian Sevcenco wrote: Hi! I am trying to rebuild the f25 srpm on a centos 7 machine but after a successful compilation i get this test error : 99% tests passed, 1 tests failed out of 454 Label Time Summary: Label1= 0.20 sec (1 test) Label2

[CMake] Potential bug: Having executables named "test" causes Ninja generator to generate ambiguous rules...

Hi, I am trying to migrate a very large project from cmake 2.8.11.2 + ninja 1.3.4 to cmake 3.7.2 + ninja 1.7.2 and found what might be a bug with the ninja generator. In my project we have a number of executables that are named "test". This is normally not a problem since each one as a

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-149-g3cffa4c

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 3cffa4c58ecdeaf44d05124a6cc2799205ca9670 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-151-g00340d9

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 00340d929ffb8986aa9349137149ae0edd28b60e (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-153-g4a46ce0

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 4a46ce0e5cad085dd7e0013ce1b3d976a2c437c2 (commit) via

Re: [cmake-developers] Debugger for CMake

On 02/13/2017 10:18 PM, Justin Berger wrote: > I agree on the maximizing code reuse, but that doesn't require them to use > the same operational mode -- the two modes do fundamentally different things Right. We shouldn't necessarily expect the server to start and then decide whether it is a code

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-62-g31e96cc

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 31e96ccca23a034700e780470bf48cff0d7fd15e (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-122-ge6f8142

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 e6f8142ae6ad655897827031acb791d15f6c2896 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-71-gdc58d9f

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 dc58d9f06d921e3e5d03b9adf9a4d9ec5359d9ba (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-64-gb7d8d80

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 b7d8d80a62d2e2c31863efedd41945c2e9db9bcf (commit) via

Re: [cmake-developers] #16633: make CTestTestfile.cmake output dir possible to control

On 02/13/2017 10:00 AM, Giel van Schijndel wrote: > I've written it as a reStructuredText document here [2]. > [2]: > https://gitlab.kitware.com/muggenhor/cmake/blob/ctest-alt-dir/Help/ctest_alt_dir.rst Thanks for the nice write-up! >From the doc: > generate a relative path from the

[Cmake-commits] CMake branch, release, updated. v3.8.0-rc1-9-gf0e5954

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, release has been updated via f0e5954fcee6b546eaa858b1e3323f529d906d04 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-74-g03be8cc

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 03be8ccbf607b378c7ffcfd2ffe6797612837efa (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-141-g47f4a0c

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 47f4a0c1ed5243f2d8482a952a0a687ab9307bd0 (commit) via

[Cmake-commits] CMake branch, release, updated. v3.8.0-rc1-13-gf45e3b9

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, release has been updated via f45e3b950991f5c4f66cd132bda61a369a3016d7 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-138-geed7ebb

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 eed7ebb5ca6bb7430e2601b94eb1d2fde40f6884 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-81-g5af61d4

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 5af61d446d53517a90806ce45060f48b511d263d (commit) via

Re: [cmake-developers] #16633: make CTestTestfile.cmake output dir possible to control

On Tue, Feb 14, 2017 at 08:23:58 -0500, Brad King wrote: > On 02/13/2017 10:00 AM, Giel van Schijndel wrote: >> I've written it as a reStructuredText document here [2]. >> [2]: >> https://gitlab.kitware.com/muggenhor/cmake/blob/ctest-alt-dir/Help/ctest_alt_dir.rst > > Thanks for the nice

Re: [cmake-developers] Debugger for CMake

19:54, 14 February 2017 г., Ben Boeckel :On Mon, Feb 13, 2017 at 20:18:02 -0700, Justin Berger wrote: I agree on the maximizing code reuse, but that doesn't require them to use the same operational mode -- the two modes do fundamentally different things; even while sharing

Re: [cmake-developers] #16633: make CTestTestfile.cmake output dir possible to control

On 02/14/2017 10:54 AM, Giel van Schijndel wrote: > I think it may be easier to do this inside CMake by generating the "new" > form of the add_test() command in the produced CTestTestfile.cmake. From > some experiments I've got the impression that that's always executed > with paths relative to

Re: [cmake-developers] Debugger for CMake

On Mon, Feb 13, 2017 at 20:18:02 -0700, Justin Berger wrote: > I agree on the maximizing code reuse, but that doesn't require them to use > the same operational mode -- the two modes do fundamentally different > things; even while sharing most internal components. Is the idea that you > could only

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-144-g20d3916

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 20d39160baf3301acdfac3f844b2c23cb1a2dd9b (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-136-gc415052

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 c415052b368c6b1dd822332b443f896841804d0e (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-155-g60c0bb2

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 60c0bb2d4a7390ce63237da1b6a3d5dfcc79bab6 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-84-g8b155a6

_VERSION_MINOR 8) -set(CMake_VERSION_PATCH 20170214) +set(CMake_VERSION_PATCH 20170215) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-129-g726660c

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 726660c22aa5116222cc0b5d713899b8fac92a24 (commit) via