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 <
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
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 us
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 (lik
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 t
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 r
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 throu
