VS 2015

Skip to first unread message

Bruce Dawson

Apr 12, 2016, 8:33:29 PM4/12/16
to Chromium-dev
VS 2015 has now been the default Windows compiler for one month and it has been decided to make this official. This means that C++ features that require VS 2015 will now be considered when discussing what language features to allow. Building with VS 2013 will no longer be supported (and hasn't worked for several weeks anyway).

VS 2015 Update 2 has numerous compiler and linker bug fixes and improved language features so Chromium developers should use Update 2 to build Chromium.

In a couple of weeks https://codereview.chromium.org/1849423002/ will be landed which will require VS 2015 Update 2 or higher.

Any questions, comments, or concerns?

Demetrios Tsillas

Apr 13, 2016, 9:03:17 AM4/13/16
to Chromium-dev
What version of chromium is confirmed to work with 2015 Update 2?


Václav Brožek

Apr 14, 2016, 8:51:28 AM4/14/16
to bruce...@chromium.org, Chromium-dev
While https://www.chromium.org/developers/how-tos/get-the-code confirms that VS 2015 is the only supported, it points to https://chromium.googlesource.com/chromium/src/+/master/docs/windows_build_instructions.md, which also speaks about VS 2013. Any knowledgeable volunteers to update that?

(When at it: The windows_build_instructions.md also refers to "Step 3, below" and "step 4 above", both of which are missing from the document. Would be great to have this fixed as well.)


Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:


Apr 14, 2016, 2:47:20 PM4/14/16
to Chromium-dev
Chromium trunk was switched to building with VS 2015 on March 11th. The change that made the switch was first branched for M51. So, M51 is the first version of Chromium that will ship being built with VS 2015.

M50 probably can build with VS 2015, perhaps with minor tweaks, but there are no plans to do this.


Apr 14, 2016, 2:49:34 PM4/14/16
to Chromium-dev, bruce...@chromium.org
I'll update windows_build_instructions.md to fix up the references to Step 3 and Step 4, and to remove the VS 2013 instructions, now that VS 2015 is officially the one-true-compiler (on Windows, not counting clang-cl).


Apr 16, 2016, 10:13:37 PM4/16/16
to Chromium-dev
With this configuration,if I build an executable which only depends on the base module,can this executable be running on Windows XP?
That is to say,can the output of VS2015's executable be running on Windows XP?

在 2016年4月13日星期三 UTC+8上午8:33:29,Bruce Dawson写道:

Scott Graham

Apr 18, 2016, 12:15:06 PM4/18/16
to lan...@gmail.com, Chromium-dev
Chrome/Chromium don't support XP any longer. VS2015 can with some restrictions.

'base' would have worked relatively recently (pre M50 branch), but things have changed so that it will not any more (SRW locks instead of CRITICAL_SECTIONs for one.)



Apr 18, 2016, 9:01:02 PM4/18/16
to Chromium-dev, lan...@gmail.com
Ah,so it is because the windows api the code use.
Could you explain the detail of "some restrictions" when using VS2015?

在 2016年4月19日星期二 UTC+8上午12:15:06,Scott Graham写道:
Reply all
Reply to author
0 new messages