[CMake] Why does CMake 3.9.0 open VS2017 when targeting 2013 after installing 2017... sigh.

[Ruben Di Battista]

What about switching to Linux? It generally does what you tell it to do. :)

(Just wanted to release a bit the tension here… Dunno how effective it
is...)
_

-.     .´  |∞∞∞∞
  ',  ;    |∞∞∞∞∞∞
    ˜˜     |∞∞∞∞∞∞∞∞∞ RdB
    ,.,    |∞∞∞∞∞∞
  .'   '.  |∞∞∞∞
-'       `’
https://rdb.is


On 15 agosto 2018 a 01:27:07, Brian Davis (bitminer at gmail.com) scritto:


It also cannot find CUDA likely as CUDA was not installed after 2017.  I
would like it to load 2013 after being told to generate Visual Studio 2013
project files.  Is this difficult to ask fo Kitware?  I am sure there are
certainly some shenanigans like path or VS2017 hooking calls to 2013 tools
or the like all of which I am sure make sens to a cubite in the bowels of
the MS machine.  VS loaded 2017 and vs 2013  proj files then promptly had
problems searching files, compiling stale targets and the like.  So while
VS2017 make "hook" 2013 tools it certainly can't do any thing useful with
them IME.  Is there a Meta buld tool (goop generator) that will build goop
for a target goop reader then call said target goop reader (of correct
specified version) to read goop and compile my code?  sigh.

-- 

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cmake.org/pipermail/cmake/attachments/20180814/c117bd56/attachment.html>