Am 15. August 2018 00:20:37 MESZ schrieb Brian Davis <bitmi...@gmail.com>:
>Why does CMake 3.9.0 open VS2017 when targeting 2013 after installing
>2017... sigh.
>
>Without even regenerating or re configuring (even though that has no
>effect
>either) when "Open Project" is selected 2017 is opened and not 2013...
>errr
>what am I targeting again? Happened after 2017 install. How does
>CMake
>Decide which app to call.... err I got a sneaky suspicion as to how....
>in
>a not so goodly way.
>
>Sure wishI could get CMake to open VS2013 with the environment vars I
>ahve
>set when it was called... guess I'll have to settle for the new and
>improved VS2017 I can't use on the project.
Or probably uses the Qt function to open the project file with the same program
that is configured in Explorer. So change it there. There is a Visual Studio
version selector but VS2017 can also open some older versions and use their
toolkits.
HS
--
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
