[Cmake-commits] CMake branch, master, updated. v3.15.2-655-g3430144
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 34301441b963a2d7e02b4a4355a6634b3bbb7977 (commit) from 7a92fb7bf675005b7d77dc6fdb157409dace52f9 (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=34301441b963a2d7e02b4a4355a6634b3bbb7977 commit 34301441b963a2d7e02b4a4355a6634b3bbb7977 Author: Kitware Robot AuthorDate: Sat Aug 17 00:01:07 2019 -0400 Commit: Kitware Robot CommitDate: Sat Aug 17 00:01:07 2019 -0400 CMake Nightly Date Stamp diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 53c1559..6ecab33 100644 --- a/Source/CMakeVersion.cmake +++ b/Source/CMakeVersion.cmake @@ -1,7 +1,7 @@ # CMake version number components. set(CMake_VERSION_MAJOR 3) set(CMake_VERSION_MINOR 15) -set(CMake_VERSION_PATCH 20190816) +set(CMake_VERSION_PATCH 20190817) #set(CMake_VERSION_RC 0) set(CMake_VERSION_IS_DIRTY 0) --- 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 https://cmake.org/mailman/listinfo/cmake-commits
Re: [CMake] How to specify VS2017 compilers when on VS2019
can just specify the 2017 generator, 2019 will load an build it just fine. If 2017 is still opening when you double-click a solution, change your default handler for .sln files to 2019. Again, 2019 can build projects as is for 2017, 2015, etc... On Fri, Aug 16, 2019 at 11:19 AM Michael Jackson < mike.jack...@bluequartz.net> wrote: > Why can't I do -T v141? > > -- > Mike Jackson > > On 8/16/19, 2:09 PM, "Kyle Edwards" wrote: > > On Fri, 2019-08-16 at 13:54 -0400, Michael Jackson wrote: > > What are the values to the -T argument that are to be used so that I > > can use VS2019 but have the 2017 compilers? > > Rather than using a -T argument, you want to set the CC environment > variable or -DCMAKE_C_COMPILER on the command line (likewise for CXX > and CMAKE_CXX_COMPILER.) > > Kyle > > > > -- > > 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: > https://cmake.org/mailman/listinfo/cmake > -- 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: https://cmake.org/mailman/listinfo/cmake
[Cmake-commits] CMake branch, master, updated. v3.15.2-654-g7a92fb7
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 7a92fb7bf675005b7d77dc6fdb157409dace52f9 (commit)
via cea253a38bb33beb64c7b36c7c75929453ec8749 (commit)
from 2beed5a4ef66f415f4efa327a8c479395d262e52 (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=7a92fb7bf675005b7d77dc6fdb157409dace52f9
commit 7a92fb7bf675005b7d77dc6fdb157409dace52f9
Merge: 2beed5a cea253a
Author: Kyle Edwards
AuthorDate: Fri Aug 16 19:37:08 2019 +
Commit: Kitware Robot
CommitDate: Fri Aug 16 15:37:20 2019 -0400
Merge topic 'clang-llvm-rc'
cea253a38b Clang: Fall back to llvm-rc when rc is unavailable
Acked-by: Kitware Robot
Acked-by: Ben Boeckel
Merge-request: !3687
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=cea253a38bb33beb64c7b36c7c75929453ec8749
commit cea253a38bb33beb64c7b36c7c75929453ec8749
Author: Gregory Mitrano
AuthorDate: Tue Aug 13 00:00:06 2019 -0400
Commit: Gregory Mitrano
CommitDate: Wed Aug 14 00:20:39 2019 -0400
Clang: Fall back to llvm-rc when rc is unavailable
This change modifies how CMAKE_RC_COMPILER is configured to improve
the out-of-box experience for developers using Clang on Windows.
The previous behavior was to require the user to explicitly specify
the resource compiler when CMake was called. The new behavior
is to automatically attempt to locate the MSVC rc binary and use that
if it's found. If rc is not available, CMake will now fall back to
Clang's llvm-rc binary.
With this change in place, trivial C/C++ programs can be generated
with Ninja and Clang on Windows without running into errors about
a missing resource compiler.
Fixes: #19318
diff --git a/Modules/Platform/Windows-Clang.cmake
b/Modules/Platform/Windows-Clang.cmake
index b317da6..728e0b9 100644
--- a/Modules/Platform/Windows-Clang.cmake
+++ b/Modules/Platform/Windows-Clang.cmake
@@ -99,6 +99,21 @@ if("x${CMAKE_C_SIMULATE_ID}" STREQUAL "xMSVC"
"or clang-cl as both C and C++ compilers.")
endif()
+ if(NOT CMAKE_RC_COMPILER_INIT)
+# Check if rc is already in the path
+# This may happen in cases where the user is already in a visual studio
environment when CMake is invoked
+find_program(__RC_COMPILER_PATH NAMES rc)
+
+# Default to rc if it's available, otherwise fall back to llvm-rc
+if(__RC_COMPILER_PATH)
+ set(CMAKE_RC_COMPILER_INIT rc)
+else()
+ set(CMAKE_RC_COMPILER_INIT llvm-rc)
+endif()
+
+unset(__RC_COMPILER_PATH CACHE)
+ endif()
+
if ( "x${CMAKE_CXX_COMPILER_FRONTEND_VARIANT}" STREQUAL "xMSVC" OR
"x${CMAKE_C_COMPILER_FRONTEND_VARIANT}" STREQUAL "xMSVC" )
include(Platform/Windows-MSVC)
---
Summary of changes:
Modules/Platform/Windows-Clang.cmake | 15 +++
1 file changed, 15 insertions(+)
hooks/post-receive
--
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
https://cmake.org/mailman/listinfo/cmake-commits
[CMake] ExternalProject install
Dear All, I try to understand the install logic for ExternalProjects. I added several CMake-based external projects to my main build, using the ExternalProject_Add() method. If I generate the build system and issue 'make install', the external projects install routines are also triggered. Is that the expected behaviour? (I have set INSTALL_COMMAND to "" in the ExternalProject_Add() call.) Is there a way, to switch this behaviour on or off? The only way I could achieve this was to put the CMakeLists.txt with the ExternalProject_Add() call into a subfolder and call that subfolder with add_subdirectory( EXCLUDE_FROM_ALL). But this is somewhat inconvinient, since I have to switch the installation on and off depending on a variable, so I have to add if(BUILD_API) add_subdirectory(...) else() add_subdirectory(... EXCLUDE_FROM_ALL) endif() branches for each subproject. Setting EXCLUDE_FROM_ALL TRUE or FALSE in ExternalProject_Add() routine did not help either. Any other suggestions? Thanks in advance. Best regards, Bálint signature.asc Description: OpenPGP digital signature -- 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: https://cmake.org/mailman/listinfo/cmake
Re: [CMake] How to specify VS2017 compilers when on VS2019
Why can't I do -T v141? -- Mike Jackson On 8/16/19, 2:09 PM, "Kyle Edwards" wrote: On Fri, 2019-08-16 at 13:54 -0400, Michael Jackson wrote: > What are the values to the -T argument that are to be used so that I > can use VS2019 but have the 2017 compilers? Rather than using a -T argument, you want to set the CC environment variable or -DCMAKE_C_COMPILER on the command line (likewise for CXX and CMAKE_CXX_COMPILER.) Kyle -- 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: https://cmake.org/mailman/listinfo/cmake
Re: [CMake] How to specify VS2017 compilers when on VS2019
On Fri, 2019-08-16 at 13:54 -0400, Michael Jackson wrote: > What are the values to the -T argument that are to be used so that I > can use VS2019 but have the 2017 compilers? Rather than using a -T argument, you want to set the CC environment variable or -DCMAKE_C_COMPILER on the command line (likewise for CXX and CMAKE_CXX_COMPILER.) Kyle -- 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: https://cmake.org/mailman/listinfo/cmake
[CMake] How to specify VS2017 compilers when on VS2019
What are the values to the -T argument that are to be used so that I can use VS2019 but have the 2017 compilers? -- Mike Jackson -- 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: https://cmake.org/mailman/listinfo/cmake
Re: [CMake] Ways to require CUDA arch minimum version?
Thanks, I am interested in enforcing minimum computing capacity (which translates to hardware restraint). If there is no such feature, would you be interested for such a feature? Hong On August 16, 2019 7:41:33 AM PDT, Robert Maynard wrote: >Are you asking for a minimum CUDA SDK version or a restriction based >on the hardware of the machine? > >We have no pre-built logic to enforce a minimum hardware component, as >we want to support building CUDA on a machine without a GPU. >As far as minimum CUDA SDK is concerned if you are doing it through >find_package(CUDA) you would check the version after and error out if >not high enough >As farm as CUDA as a first class language, you can check the >CMAKE_CUDA_COMPILER_VERSION and error out. > >On Thu, Aug 15, 2019 at 9:34 PM Hong Xu wrote: >> >> Is there a way to enforce a minimum CUDA arch version when finding >CUDA? >> Hong >> >> -- >> >> 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: >> https://cmake.org/mailman/listinfo/cmake -- 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: https://cmake.org/mailman/listinfo/cmake
Re: [CMake] Ways to require CUDA arch minimum version?
Are you asking for a minimum CUDA SDK version or a restriction based on the hardware of the machine? We have no pre-built logic to enforce a minimum hardware component, as we want to support building CUDA on a machine without a GPU. As far as minimum CUDA SDK is concerned if you are doing it through find_package(CUDA) you would check the version after and error out if not high enough As farm as CUDA as a first class language, you can check the CMAKE_CUDA_COMPILER_VERSION and error out. On Thu, Aug 15, 2019 at 9:34 PM Hong Xu wrote: > > Is there a way to enforce a minimum CUDA arch version when finding CUDA? > Hong > > -- > > 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: > https://cmake.org/mailman/listinfo/cmake -- 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: https://cmake.org/mailman/listinfo/cmake
