date:20170326

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc3-566-gdeec891

2017-03-26 Thread Kitware Robot

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  deec8919ba8e2a0f469346a4a47300e618f6e83c (commit)
  from  d6ef21cf702793b8c1ca74e1243c357e651b6adf (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
---

Summary of changes:
 Source/CMakeVersion.cmake |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-584-gd46bcf6

2017-03-26 Thread Kitware Robot

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
  discards  ec5a687ebe40567ad8217ab29ba2e5a25ac4a71b (commit)
  discards  5319e9c2e6631549e9dbe284237e179110082e6c (commit)
  discards  d6eab9516fda3e50c14abe942e014a8a564f7697 (commit)
  discards  95e1bd59d86542f2e73b5f3266e10730e766ca9a (commit)
  discards  fd61926921afe2920aee3e5a17fc66e5383bf010 (commit)
  discards  ed09bd8bad52401ad899a2f3994ef2bbccb738b8 (commit)
  discards  57fa214f883c593f79ef4573b7fad716d3578416 (commit)
   via  d46bcf677806ecc9e7116bd88b3f51954e301e8e (commit)
   via  839bfaa1b72a3e1482afe27cba8d3d8ea22038ec (commit)
   via  7c60cc5daae2dbecfe8ddb02142c1fe08935b161 (commit)
   via  2d6cff418688284b9936e121db5b1d5292e7c0fc (commit)
   via  e0ad6d2d1e872e1c4aecdf0e4e1c16b9cca4c6c2 (commit)
   via  2bb4956dbfc4408bbc1b1e993a81356d0fd90050 (commit)
   via  02d721316224bbb9029d6d76956b7824990091a3 (commit)
   via  deec8919ba8e2a0f469346a4a47300e618f6e83c (commit)

This update added new revisions after undoing existing revisions.  That is
to say, the old revision is not a strict subset of the new revision.  This
situation occurs when you --force push a change and generate a repository
containing something like this:

 * -- * -- B -- O -- O -- O (ec5a687ebe40567ad8217ab29ba2e5a25ac4a71b)
\
 N -- N -- N (d46bcf677806ecc9e7116bd88b3f51954e301e8e)

When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=d46bcf677806ecc9e7116bd88b3f51954e301e8e
commit d46bcf677806ecc9e7116bd88b3f51954e301e8e
Merge: 839bfaa c6653ec
Author: Domen Vrankar 
AuthorDate: Sun Mar 26 21:56:38 2017 +
Commit: Kitware Robot 
CommitDate: Mon Mar 27 00:01:28 2017 -0400

Stage topic 'cpack-rpm-use-current-cmake-policies'

Topic-id: 23288
Topic-url: https://gitlab.kitware.com/cmake/cmake/merge_requests/631


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=839bfaa1b72a3e1482afe27cba8d3d8ea22038ec
commit 839bfaa1b72a3e1482afe27cba8d3d8ea22038ec
Merge: 7c60cc5 0527046
Author: Domen Vrankar 
AuthorDate: Sun Mar 26 00:08:35 2017 +
Commit: Kitware Robot 
CommitDate: Mon Mar 27 00:01:28 2017 -0400

Stage topic 'cpack-rpm-debuginfo-docs-cleanup'

Topic-id: 23284
Topic-url: https://gitlab.kitware.com/cmake/cmake/merge_requests/630


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7c60cc5daae2dbecfe8ddb02142c1fe08935b161
commit 7c60cc5daae2dbecfe8ddb02142c1fe08935b161
Merge: 2d6cff4 58d6061
Author: Domen Vrankar 
AuthorDate: Sat Mar 25 19:28:21 2017 +
Commit: Kitware Robot 
CommitDate: Mon Mar 27 00:01:28 2017 -0400

Stage topic 'cpack-rpm-tests-handle-build-id-links'

Topic-id: 23282
Topic-url: https://gitlab.kitware.com/cmake/cmake/merge_requests/628


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2d6cff418688284b9936e121db5b1d5292e7c0fc
commit 2d6cff418688284b9936e121db5b1d5292e7c0fc
Merge: e0ad6d2 f237f5f
Author: Domen Vrankar 
AuthorDate: Sat Mar 25 14:26:35 2017 +
Commit: Kitware Robot 
CommitDate: Mon Mar 27 00:01:27 2017 -0400

Stage topic 'cpack-rpm-debuginfo-honor-package-filename'

Topic-id: 23243
Topic-url: https://gitlab.kitware.com/cmake/cmake/merge_requests/620


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e0ad6d2d1e872e1c4aecdf0e4e1c16b9cca4c6c2
commit e0ad6d2d1e872e1c4aecdf0e4e1c16b9cca4c6c2
Merge: 2bb4956 e9fc7ff
Author: Daniel Pfeifer 
AuthorDate: Fri Mar 24 22:04:21 2017 +
Commit: Kitware Robot 
CommitDate: Mon Mar 27 00:01:26 2017 -0400

Stage topic 'cm-sys-stat'

Topic-id: 23273
Topic-url: https://gitlab.kitware.com/cmake/cmake/merge_requests/625


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2bb4956dbfc4408bbc1b1e993a81356d0fd90050
commit 2bb4956dbfc4408bbc1b1e993a81356d0fd90050
Merge: 02d7213 ea2a91a
Author: Brad King 
AuthorDate: Fri Mar 24 19:22:04 2017 +
Commit: Kitware Robot 
CommitDate: Mon Mar 27 00:01:26 2017 -0400

Stage topic 'update-kwsys'

Topic-id: 23265
Topic-url: https://gitlab.kitware.com/cmake/cmake/merge_requests/624

[Cmake-commits] CMake branch, nightly-master, updated. v3.8.0-rc3-565-gd6ef21c

2017-03-26 Thread Kitware Robot

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, nightly-master has been updated
   via  d6ef21cf702793b8c1ca74e1243c357e651b6adf (commit)
  from  3ac205f7dcbb0e0b0aa058cc9b8d84f0318d02d5 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
---

Summary of changes:
 Source/CMakeVersion.cmake |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, nightly, updated. v3.8.0-rc3-583-gec5a687

2017-03-26 Thread Kitware Robot

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, nightly has been updated
  discards  e18fda65ab5b5b56c87b89f7c2ba9fc879d87d7b (commit)
  discards  a209a3bce2e8bc3100a3de2b36349996fc18adb6 (commit)
  discards  6d6df438eaa5f0e21591142ba23681661968daf8 (commit)
  discards  85994c65a43f0a171e5e52afcb6eef0031a87744 (commit)
  discards  55a5616ac24da31d63744b84f07b531bb7e837f4 (commit)
  discards  239a17c59f75b0c1294009703ddd6dd0f24b644d (commit)
   via  ec5a687ebe40567ad8217ab29ba2e5a25ac4a71b (commit)
   via  c6653ec59f510af6ab550065e127e45cf2f4a457 (commit)
   via  5319e9c2e6631549e9dbe284237e179110082e6c (commit)
   via  d6eab9516fda3e50c14abe942e014a8a564f7697 (commit)
   via  95e1bd59d86542f2e73b5f3266e10730e766ca9a (commit)
   via  fd61926921afe2920aee3e5a17fc66e5383bf010 (commit)
   via  ed09bd8bad52401ad899a2f3994ef2bbccb738b8 (commit)
   via  57fa214f883c593f79ef4573b7fad716d3578416 (commit)
   via  d6ef21cf702793b8c1ca74e1243c357e651b6adf (commit)

This update added new revisions after undoing existing revisions.  That is
to say, the old revision is not a strict subset of the new revision.  This
situation occurs when you --force push a change and generate a repository
containing something like this:

 * -- * -- B -- O -- O -- O (e18fda65ab5b5b56c87b89f7c2ba9fc879d87d7b)
\
 N -- N -- N (ec5a687ebe40567ad8217ab29ba2e5a25ac4a71b)

When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
---

Summary of changes:
 Modules/CPackRPM.cmake|   69 +++--
 Source/CMakeVersion.cmake |2 +-
 2 files changed, 23 insertions(+), 48 deletions(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-583-gec5a687

2017-03-26 Thread Kitware Robot

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  ec5a687ebe40567ad8217ab29ba2e5a25ac4a71b (commit)
   via  c6653ec59f510af6ab550065e127e45cf2f4a457 (commit)
  from  5319e9c2e6631549e9dbe284237e179110082e6c (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ec5a687ebe40567ad8217ab29ba2e5a25ac4a71b
commit ec5a687ebe40567ad8217ab29ba2e5a25ac4a71b
Merge: 5319e9c c6653ec
Author: Domen Vrankar 
AuthorDate: Sun Mar 26 21:56:38 2017 +
Commit: Kitware Robot 
CommitDate: Sun Mar 26 17:56:41 2017 -0400

Stage topic 'cpack-rpm-use-current-cmake-policies'

Topic-id: 23288
Topic-url: https://gitlab.kitware.com/cmake/cmake/merge_requests/631


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c6653ec59f510af6ab550065e127e45cf2f4a457
commit c6653ec59f510af6ab550065e127e45cf2f4a457
Author: Domen Vrankar 
AuthorDate: Sat Mar 25 21:01:59 2017 +0100
Commit: Domen Vrankar 
CommitDate: Sun Mar 26 23:55:15 2017 +0200

CPack/RPM: always use current CMake version policies

diff --git a/Modules/CPackRPM.cmake b/Modules/CPackRPM.cmake
index 95263ed..c0f432d 100644
--- a/Modules/CPackRPM.cmake
+++ b/Modules/CPackRPM.cmake
@@ -898,6 +898,8 @@
 
 # Author: Eric Noulard with the help of Alexander Neundorf.
 
+cmake_policy(VERSION "${CMAKE_VERSION}")
+
 function(get_unix_permissions_octal_notation PERMISSIONS_VAR RETURN_VAR)
   set(PERMISSIONS ${${PERMISSIONS_VAR}})
   list(LENGTH PERMISSIONS PERM_LEN_PRE)
@@ -979,12 +981,7 @@ function(cpack_rpm_prepare_relocation_paths)
   endforeach()
 
   # warn about all the paths that are not relocatable
-  cmake_policy(PUSH)
-# Tell file(GLOB_RECURSE) not to follow directory symlinks
-# even if the project does not set this policy to NEW.
-cmake_policy(SET CMP0009 NEW)
-file(GLOB_RECURSE FILE_PATHS_ "${WDIR}/*")
-  cmake_policy(POP)
+  file(GLOB_RECURSE FILE_PATHS_ "${WDIR}/*")
   foreach(TMP_PATH ${FILE_PATHS_})
 string(LENGTH "${WDIR}" WDIR_LEN)
 string(SUBSTRING "${TMP_PATH}" ${WDIR_LEN} -1 TMP_PATH)
@@ -1011,10 +1008,7 @@ endfunction()
 
 function(cpack_rpm_prepare_content_list)
   # get files list
-  cmake_policy(PUSH)
-cmake_policy(SET CMP0009 NEW)
-file(GLOB_RECURSE CPACK_RPM_INSTALL_FILES LIST_DIRECTORIES true RELATIVE 
"${WDIR}" "${WDIR}/*")
-  cmake_policy(POP)
+  file(GLOB_RECURSE CPACK_RPM_INSTALL_FILES LIST_DIRECTORIES true RELATIVE 
"${WDIR}" "${WDIR}/*")
   set(CPACK_RPM_INSTALL_FILES "/${CPACK_RPM_INSTALL_FILES}")
   string(REPLACE ";" ";/" CPACK_RPM_INSTALL_FILES "${CPACK_RPM_INSTALL_FILES}")
 
@@ -1033,10 +1027,7 @@ function(cpack_rpm_prepare_content_list)
 set(_DISTINCT_PATH "${_RPM_RELOCATION_PREFIX}")
 
 string(REPLACE "/" ";" _CPACK_RPM_PACKAGE_PREFIX_ELEMS " 
${_RPM_RELOCATION_PREFIX}")
-cmake_policy(PUSH)
-  cmake_policy(SET CMP0007 NEW)
-  list(REMOVE_AT _CPACK_RPM_PACKAGE_PREFIX_ELEMS -1)
-cmake_policy(POP)
+list(REMOVE_AT _CPACK_RPM_PACKAGE_PREFIX_ELEMS -1)
 unset(_TMP_LIST)
 # Now generate all of the parent dirs of the relocation path
 foreach(_PREFIX_PATH_ELEM ${_CPACK_RPM_PACKAGE_PREFIX_ELEMS})
@@ -1878,19 +1869,15 @@ function(cpack_rpm_generate_package)
 endif()
 
 if(DEFINED CPACK_RPM_PACKAGE_${_RPM_SPEC_HEADER})
-  cmake_policy(PUSH)
-cmake_policy(SET CMP0057 NEW)
-# Prefix can be replaced by Prefixes but the old version stil works so 
we'll ignore it for now
-# Requires* is a special case because it gets transformed to 
Requires(pre/post/preun/postun)
-# Auto* is a special case because the tags can not be queried by 
querytags rpmbuild flag
-set(special_case_tags_ PREFIX REQUIRES_PRE REQUIRES_POST 
REQUIRES_PREUN REQUIRES_POSTUN AUTOPROV AUTOREQ AUTOREQPROV)
-if(NOT _RPM_SPEC_HEADER IN_LIST RPMBUILD_TAG_LIST AND NOT 
_RPM_SPEC_HEADER IN_LIST special_case_tags_)
-  cmake_policy(POP)
-  message(AUTHOR_WARNING "CPackRPM:Warning: ${_RPM_SPEC_HEADER} not "
-  "supported in provided rpmbuild. Tag will not be used.")
-  continue()
-endif()
-  cmake_policy(POP)
+  # Prefix can be replaced by Prefixes but the old version stil works so 
we'll ignore it for now
+  # Requires* is a special case because it gets transformed to 
Requires(pre/post/preun/postun)
+  # Auto* is a special case because the tags can not be queried by 
querytags rpmbuild flag
+  set(special_case_tags_ PREFIX REQUIRES_PRE

[CMake] Visual Studio 2017 could not be found if installed in non-default location

2017-03-26 Thread HarpyWar

*CMake could not find Visual Studio 2017 and stops with error:*
-- The CXX compiler identification is unknown


Initially Visual Studio Community was installed in path:
E:\Microsoft
But actually part of files are also located in default installation path:

C:\Program Files (x86)\Microsoft Visual Studio\2017\Community

The files tree from both these directories
https://forums.pvpgn.pro/misc.php?action=pan_download=17=1


Output from vswhere.exe shows that Visual Studio is installed on disk C:\
(https://github.com/Microsoft/vswhere)

Visual Studio Locator, version 1.0.58Copyright (C) Microsoft
Corporation. All rights reserved.

instanceId: 3a7dda28
installDate: 23.11.2016
installationName: VisualStudio/15.0.0+26228.9
installationPath: C:\Program Files (x86)\Microsoft Visual Studio\2017\Community
installationVersion: 15.0.26228.9
displayName: Visual Studio Community 2017
description: Бесплатная полнофункциональная интегрированная среда разработки для
 учащихся, разработчиков решений с открытым кодом и индивидуальных разработчиков

enginePath: C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\a
pp\ServiceHub\Services\Microsoft.VisualStudio.Setup.Service
channelId: VisualStudio.15.Release
channelPath: C:\Users\User\AppData\Local\Microsoft\VisualStudio\Packages\_Channe
ls\4CB340F5\catalog.json
channelUri: https://aka.ms/vs/15/release/channel
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] Is it possible to run ctest outside build tree?

2017-03-26 Thread Craig Scott

Not sure if this is the sort of thing you are looking for, but you can use
the cmake -E chdir command as a way to run an arbitrary command from
another directory without having to create any extra scripts, perform shell
logic, etc. For example:

cmake -E chdir /my/build/tree ctest 




On Sun, Mar 26, 2017 at 7:29 PM, Eric Noulard 
wrote:

> This works but it is not possible to pass filtering argument (-L or -R) to
> ctest this way.
>
> Le 26 mars 2017 10:13, "Dvir Yitzchaki"  a
> écrit :
>
>> How about
>>
>>
>>
>> cmake --build /my/build/tree --target test
>>
>>
>>
>> Regards,
>>
>> Dvir
>>
>>
>>
>> *From:* CMake [mailto:cmake-boun...@cmake.org] *On Behalf Of *Eric
>> Noulard
>> *Sent:* Friday, March 24, 2017 13:04
>> *To:* CMake Mailinglist 
>> *Subject:* [CMake] Is it possible to run ctest outside build tree?
>>
>>
>>
>> Is possible to run ctest outside the builld tree and how?
>>
>> typical use is when I have an out of source build I may be in the source
>> tree
>>
>> and want to run tests without manually going to build tree.
>>
>>
>>
>> i.e. I currently do:
>>
>>
>>
>> ninja -C /my/build/tree
>>
>>
>>
>> is there a similar way to do that with ctest (other than creating my own
>> script, shell alias etc...)?
>>
>>
>>
>> --
>>
>> Eric
>>
>
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/cmake
>



-- 
Craig Scott
Melbourne, Australia
https://crascit.com
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] Is it possible to run ctest outside build tree?

2017-03-26 Thread Dvir Yitzchaki

How about

cmake --build /my/build/tree --target test

Regards,
Dvir

From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Eric Noulard
Sent: Friday, March 24, 2017 13:04
To: CMake Mailinglist 
Subject: [CMake] Is it possible to run ctest outside build tree?

Is possible to run ctest outside the builld tree and how?
typical use is when I have an out of source build I may be in the source tree
and want to run tests without manually going to build tree.

i.e. I currently do:

ninja -C /my/build/tree

is there a similar way to do that with ctest (other than creating my own 
script, shell alias etc...)?

--
Eric
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] Is it possible to run ctest outside build tree?

2017-03-26 Thread Eric Noulard

This works but it is not possible to pass filtering argument (-L or -R) to
ctest this way.

Le 26 mars 2017 10:13, "Dvir Yitzchaki"  a
écrit :

> How about
>
>
>
> cmake --build /my/build/tree --target test
>
>
>
> Regards,
>
> Dvir
>
>
>
> *From:* CMake [mailto:cmake-boun...@cmake.org] *On Behalf Of *Eric Noulard
> *Sent:* Friday, March 24, 2017 13:04
> *To:* CMake Mailinglist 
> *Subject:* [CMake] Is it possible to run ctest outside build tree?
>
>
>
> Is possible to run ctest outside the builld tree and how?
>
> typical use is when I have an out of source build I may be in the source
> tree
>
> and want to run tests without manually going to build tree.
>
>
>
> i.e. I currently do:
>
>
>
> ninja -C /my/build/tree
>
>
>
> is there a similar way to do that with ctest (other than creating my own
> script, shell alias etc...)?
>
>
>
> --
>
> Eric
>
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc3-566-gdeec891

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-584-gd46bcf6

[Cmake-commits] CMake branch, nightly-master, updated. v3.8.0-rc3-565-gd6ef21c

[Cmake-commits] CMake branch, nightly, updated. v3.8.0-rc3-583-gec5a687

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-583-gec5a687

[CMake] Visual Studio 2017 could not be found if installed in non-default location

Re: [CMake] Is it possible to run ctest outside build tree?

Re: [CMake] Is it possible to run ctest outside build tree?

Re: [CMake] Is it possible to run ctest outside build tree?

9 matches

Site Navigation

Mail list logo

Footer information