ANN: VS2010 to become the main toolchain on Windows

[Carlos Pizano]

As it stands today, the preferred Windows toolchain is VS2008. This is
what we use today to build official chrome and that is why most
Windows bots use it as well.

But times change. We can't build the bits we need for Windows 8 using
VS2008. So that means that the official build will be done with
VS2010, which means it will become the preferred toolchain for chrome/
chromium. But fear not; this has happened before (when we phased out
VS2005) and it will happen again.

Here is what it is going to happen:
1- Official builders will be transitioned to VS2010 (in a week or
less)
2- Default trybots will be transitioned to VS2010, with VS2008 bots
available via --bot (real soon now)
3- Waterfall bots will transition to be mostly VS2010, with a minority
of VS2008 bots (few weeks)

For the average developer there is no immediate action needed. Support
for VS2008 is not going to disappear overnight. We haven't decided for
how long to keep supporting it but no less than 5 months. Now, if you
are setting a development machine now, I strongly recommend you start
with VS2010.

[Chris Bentzel]

The red squiggle lines indicating "future compile fail" in VS2010 are also a marked improvement over VS2008.

--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
   http://groups.google.com/a/chromium.org/group/chromium-dev

[Hironori Bono (坊野 博典)]

Greetings Carlos,

It is indeed a good new for me, who uses Visual Studio 2010. :)
By the way, out of curiosity., would it be possible to give me if
someone works for GYP Issue 222 written in this page
<http://dev.chromium.org/developers/how-tos/build-instructions-windows#TOC-Setting-up-the-environment-for-Visual-Studio-2010>?
(When I build Chromium with Visual Studio 2010 and run it on my PC, I
cannot see tooltips as written in this page.)

Regards,

Hironori Bono
E-mail: hb...@chromium.org

[Paweł Hajdan, Jr.]

On Mon, May 7, 2012 at 4:22 PM, Carlos Pizano <c...@chromium.org> wrote:

Now, if you
are setting a development machine now, I strongly recommend you start
with VS2010.

Could you update http://dev.chromium.org/developers/how-tos/build-instructions-windows to reflect that?

[Gabriel Charette]

In switching to VS2010 for builders you might also want to consider this gyp bug:  http://code.google.com/p/gyp/issues/detail?id=266&thanks=266&ts=1336742804#makechanges 

This makes it so that our chrome.exe.manifest, setup.exe.manifest, and chrome.dll.manifest are not embedded in the resulting targets, the default VS manifest is instead.

Cheers,

Gab