I was thinking it would be nice to support VS2010 as long as any of our main 
channels use it -- meaning we could drop it on the first day of 39. But I have 
no practical justification for that. If it causes a burden on Skia work then it 
might be reasonable to switch sooner.

> This set: http://chromium-cpp.appspot.com/
What MS compiler does that list require? There's a number of people building 
with VS2012, would that still be supported?

David

----- Original Message -----
> From: "Jeff Muizelaar" <jmuizel...@mozilla.com>
> To: "Ehsan Akhgari" <ehsan.akhg...@gmail.com>
> Cc: "dev-platform@lists.mozilla.org list" <dev-platform@lists.mozilla.org>
> Sent: Friday, October 17, 2014 9:14:19 AM
> Subject: Re: Compiler version expectations
> 
> 
> On Oct 16, 2014, at 3:57 PM, Ehsan Akhgari <ehsan.akhg...@gmail.com> wrote:
> 
> > On 2014-10-16, 3:49 PM, Jeff Muizelaar wrote:
> >> After some discussion some IRC it was clear that our compiler deprecation
> >> schedule is not very clear.
> >> 
> >> Now that we’re using VS2013 on trunk and will soon not being using GCC 4.4
> >> for B2G, I expect we’ll be dropping support for building with VS2010 and
> >> GCC 4.4  in the near term.
> > 
> > GCC is https://bugzilla.mozilla.org/show_bug.cgi?id=1077549.  No specific
> > bug or plans for MSVC2010, but I'd be open to killing support for it on
> > the next release train.
> > 
> >> This is important to us because Skia is planing on using more C++11
> >> features in the near term and we’d like to continue updating from
> >> upstream. Are there reasons we can’t drop support for these compilers in
> >> the 37-38 time frame?
> > 
> > What C++11 features specifically?
> 
> This set: http://chromium-cpp.appspot.com/
> 
> -Jeff
> 
> _______________________________________________
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
> 
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to