[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: |
| 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. |