[SERVER-30134] scons cannot support VS2017 when build MongoDB Created: 14/Jul/17  Updated: 27/Oct/23  Resolved: 17/Jul/17

Status: Closed
Project: Core Server
Component/s: Build
Affects Version/s: None
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: KarenHuang [X] Assignee: Andrew Morrow (Inactive)
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Participants:

 Description   

scons cannot support VS2017 when build MongoDB. Recently we moved from VS2015 to VS2017. And found MongDB failed to build. Could you please let us know how we can build MongoDB using scons with VS2017? Thanks in advance!

The following is the build information:
[executing command] scons all -j4 CXXFLAGS=""
scons: Reading SConscript files ...
Mkdir("build\scons")
scons version: 2.5.1
python version: 2 7 13 'final' 0
scons: warning: No version of Visual Studio compiler found - C/C++ compilers most likely not set correctly
File "D:\MongoDB\src\SConstruct", line 873, in <module>
Checking whether the C compiler works... no
C compiler cl doesn't work
See D:\MongoDB\src\build\scons\config.log for details



 Comments   
Comment by Andrew Morrow (Inactive) [ 14/Jul/17 ]

Hi KarenHuang2017 -

Unfortunately, at this time SCons itself does not support VS2017. Worse, it appears that Microsoft has fundamentally altered the way toolchain discovery works, meaning that the previous fail-safe way of informing SCons of where the toolchain lives (MSVC_USE_SCRIPT), no longer functions.

Please see this scons-users thread for discussion: https://pairlist4.pair.net/pipermail/scons-users/2017-January/005607.html

However, even if that were not a blocking issue, we have not yet qualified VS2017 as a supported toolchain by adding it to our continuous integration suite and ensuring that all of our regression tests pass.

Until we have done so, we recommend building MongoDB with VS2015.

Generated at Thu Feb 08 04:22:47 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.