You can use that method so you get the IDE features of VS2019 but the
VS2017 compiler.
On Fri, Aug 16, 2019 at 2:19 PM Michael Jackson
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
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 <
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
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
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
