-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Support building with VS2019 Preview #22525
Conversation
@@ -13,6 +13,7 @@ You must install several components to build the CoreCLR and CoreFX repos. These | |||
Visual Studio must be installed. Supported versions: | |||
- [Visual Studio 2015](https://www.visualstudio.com/vs/older-downloads/) (Community, Professional, Enterprise). The community version is completely free. | |||
- [Visual Studio 2017](https://www.visualstudio.com/downloads/) (Community, Professional, Enterprise). The community version is completely free. | |||
- [Visual Studio 2019 Preview](https://visualstudio.microsoft.com/vs/preview/) (Community, Professional, Enterprise). The community version is completely free. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The exact workloads required should probably be figured out. It might be worth updating the VS2017 entries as well (as it specifies more than actually required in the latest release).
Worth noting the following warnings:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm thanks for the change!
Seems there is also an error when compiling the tests:
All other tests compile successfully. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@jashook, what would you recommend to deal with the singular test project that fails to compile under VS 2019 (see #22525 (comment))? |
It might be worth noting that, refactoring the code file (so that each |
Seems like changing it to allow it to compile seems correct to me. /cc @RussKeldorph opinion? |
I imagine we will want to log a bug with the VC++ team as well. |
Added a commit removing the VS2015 support, as per the comment from @jkotas here: #22525 (comment) I think everything (modulo the VC++ bug, which I am logging now) should be addressed now and this should be ready to merge after the tests complete. |
DevDiv#789922 was logged to track the C++ compiler issue that showed up for |
* Ensure you have installed at least [Visual Studio 2015 Update 3](https://www.visualstudio.com/en-us/news/releasenotes/vs2015-update3-vs). | ||
* Make sure that you install "VC++ Tools". By default, they will not be installed. | ||
* To build for Arm32, Make sure that you have the Windows SDK for Windows 10 installed (or selected to be installed as part of VS installation). To explicitly install Windows SDK, download it from here: [Windows SDK for Windows 10](https://developer.microsoft.com/en-us/windows/downloads) | ||
- [Visual Studio 2019 Preview](https://visualstudio.microsoft.com/vs/preview/) (Community, Professional, Enterprise). The community version is completely free. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It should have been noted that the CMake version needs to be 3.14-rc for VS 2019.
* Support building with VS2019 Preview * Fixing gen-buildsys-win to only set the architecture for the VS generator * Refactoring Dev11/147911/fpcw.cpp so that it compiles under VS2019 * Removing the remaining traces of VS2015 build support Commit migrated from dotnet/coreclr@f077060
Resolves https://github.com/dotnet/coreclr/issues/22446