Every time I create a superbuild using ExternalProject_Add sooner or
later a project will not support cmake, but will have buried within its
bowels a visual studio solution project .sln and sometimes gobs of
.vcxproj files (read CPython). Now ofcourse include_external_msproject
can do this.
I have a CMake-based build that creates about 170 binaries (most of them
are individual unit test programs).
I have set the CMAKE_EXE_LINKER_FLAGS to a set of flags I wanted on all
the binaries.
Now it turns out that I need to remove, or not set, one specific flag on
a small number (like 5) of
_VERSION_MINOR 7)
-set(CMake_VERSION_PATCH 20170111)
+set(CMake_VERSION_PATCH 20170112)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
Hello,
First of all, I have been using CMake for a few years now, it is awesome
tool, thank you.
The only problem I currently have with CMake is its language, which has not
really intended to be one. After reading a few endless discussions about
this topic, I decided to give it a try and do
There are two big issues with the check_function_exists() module that I've
run into, and that others have also encountered:
(1) It can't detect functions that are inlined in system headers or
specified as a #define macro. (see
https://cmake.org/pipermail/cmake-developers/2015-July/025766.html)
I believe you will want to use the low level command CUDA_WRAP_SRCS
with the MODULE option. Since CUDA_WRAP_SRCS is a low level command,
If you need separable compilation you will need to manually invoke
those steps too ( read CUDA_SEPARABLE_COMPILATION documentation on
what methods you will need
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 3dd0616af3c5928e5c880186d5cfd241506a4369 (commit)
via
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 a37e6e27efa5729c6136105f6bd702986050d58c (commit)
via
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 aedbd25e061fc348bd2b88862956d972a955059b (commit)
via
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 d3c7c8008643475c656562837bf3c072e57ef799 (commit)
via
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 e80f026bd36fbfe70b0d88caa81bed429ca81b11 (commit)
via
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 6ec6ac205967a40297e8d3b9c0ca9d27863ef8c5 (commit)
via
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 ef155cf6403be058f878d046045e111a1bff41d8 (commit)
via
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 5c6d51bdf072a8fb6e683636321e57430c0268ac (commit)
via
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 ee14e5aaa12451d93a0cc3787d2f73b2841ec950 (commit)
via
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 afd1fd49695b0dad9cca6f00749384568c214a9e (commit)
via
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 6a7f9c025da31eff3cd63dd85c16dc5aad0534fe (commit)
via
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 74a03183ffc0982cd948bf76ce84f7891b585d1e (commit)
via
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 e9d3557ccc4b26503aa7d59ec2eaf179c9924a5b (commit)
via
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 c16ab966d519e8d8cb7bb073cc9b3e8d507b5cca (commit)
via
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 e0cc40ed58a16f63a26cf25c56f6e8471401fbfe (commit)
via
Dear All,
I'm currently using CMake-3.7.1 to build a big project with different TI
compilers (cl6x, armcl, cl-arp32) and since several months ago I started
to use linker response files because the linker command line was too long
for Windows and the build was failing.
When I tried to do this
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 374e984b7e143008d38b7d148b1700cadbccbb59 (commit)
via
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 7f3e96623e6d1bc22e447926926409c2836e7d6a (commit)
via
On 01/11/2017 08:33 AM, Gregor Jasny via CMake wrote:
> I wonder if there is a reason why no MSVC15 variable is available for
> Visual Studio 2017?
The values correspond to the toolset versions:
* https://cmake.org/cmake/help/v3.7/variable/MSVC14.html
and VS 2017 uses toolset version v141
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 016ec962653d5f2060ebf05d09ecddc13deb0cab (commit)
via
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 039588e335fbf559f66719aff2a3c8920a078261 (commit)
via
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 474edf75f6234a9ed3b59b7e11c53d57f9bd2f78 (commit)
via
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 bc2cc80255c64bc2b2fa4c9dbb54f5cd90150982 (commit)
via
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 2eb5596503ab8cf2f5ded140d45aa013c9705436 (commit)
via
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 0884c9e46a108e8d7b52f6d96242f147ab12d001 (commit)
via
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 34745595c3b87279b92ea402fd2ccb6351344307 (commit)
via
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 396e9378a820cc5216aecce6bff42f526f4f7c26 (commit)
via
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 d1682a8514f9ecbe91f59e651be917afec044907 (commit)
via
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 22dfda11121c2b0c2374a5eb29fd3a2f140ff92c (commit)
via
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 a8b576244f729e543795750eb6c9e188c0e1fe66 (commit)
via
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 ff6a034e0bb7731c97a90afec849d8c80e2a783d (commit)
via
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 1406408e61a001728eded5a7f28f3c392ff31c38 (commit)
via
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 3f697a732c4d737fa319020e435f43d973a29901 (commit)
via
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 2e8f576a9d8b320f420aca2aaf0ac51bf1f8a5c3 (commit)
via
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 69d0bac3bb25152fa0b3c4b23139b2bddb96eed2 (commit)
via
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 cae7d6db19197200455de775d457d0cbd4bb655d (commit)
via
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 0655d616d6e11b6e490b4cea2f1367caec36c4e2 (commit)
via
Hello,
I wonder if there is a reason why no MSVC15 variable is available for
Visual Studio 2017? I'm using those MSVCxx variables and
CMAKE_GENERATOR_TOOLSET to detect the active toolset:
# Visual Studio 2008
if((MSVC90 AND "${CMAKE_GENERATOR_TOOLSET}" STREQUAL "") OR
44 matches
Mail list logo
