MantisBT
Mantis Bug Tracker Workflow

View Revisions: Issue #29129 All Revisions ] Back to Issue ]
Summary 0029129: Incomplete support of MSVS2017
Revision 2017-09-20 21:01 by aml
Description I have faced with couple of problems related to the MSVS2017 support.
I use MSVS2017.3 community.

1) occt_macro file:
"macro (OCCT_MAKE_COMPILER_SHORT_NAME)" method

...
    elseif (MSVC12)
      set (COMPILER vc12)
    elseif (MSVC14)
      set (COMPILER vc14)
    elseif (MSVC15)
      # Since Visual Studio 15 (2017), its version diverged from version of
      # compiler which is 14.1; as that compiler uses the same run-time as 14.0,
      # we keep its id as "vc14" to be compatibille
      set (COMPILER vc14)
    endif()
...
there is no "MSVC15" variable. MSVS2017 utilizes the same variable "MSVC14".

I have found the following message in CMake tracker:
" There is no MSVC15 variable because VS 2017 uses the v141 toolset which is compatible with the VS 2015 v140 toolset. We may not add any more MSVC## variables now that VS versions and toolset versions have been decoupled. MSVC_VERSION is a more general value that places like InstallRequiredSystemLibraries.cmake could use instead. "
Revision 2017-09-20 19:48 by aml
Description I have faced with couple of problems related to the MSVS2017 support.
I use MSVS2017.3 community.

1) occt_macro file:
"macro (OCCT_MAKE_COMPILER_SHORT_NAME)" method

...
    elseif (MSVC12)
      set (COMPILER vc12)
    elseif (MSVC14)
      set (COMPILER vc14)
    elseif (MSVC15)
      # Since Visual Studio 15 (2017), its version diverged from version of
      # compiler which is 14.1; as that compiler uses the same run-time as 14.0,
      # we keep its id as "vc14" to be compatibille
      set (COMPILER vc14)
    endif()
...
there is no "MSVC15" variable. MSVS2017 utilizes the same variable "MSVC14".

2) I got incorrect directories structure after install. Please look at the attached image for additional details.


I have found the following message in CMake tracker:
" There is no MSVC15 variable because VS 2017 uses the v141 toolset which is compatible with the VS 2015 v140 toolset. We may not add any more MSVC## variables now that VS versions and toolset versions have been decoupled. MSVC_VERSION is a more general value that places like InstallRequiredSystemLibraries.cmake could use instead. "


Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker