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 th
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 t
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 for
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 which
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 (CMAKE_GENERATOR_TO
