Regarding upgrading to Visual C++ 2017, I have patchset for that here: https://bugs.webkit.org/show_bug.cgi?id=172412
Unfortunately it seems to cause a problem WebCore::HTMLNames::init(), which is something to do with the disabling of static constructors. On 18 July 2017 at 07:56, Carlos Alberto Lopez Perez <[email protected]> wrote: > On 05/07/17 17:10, Michael Catanzaro wrote: > > On Wed, Jul 5, 2017 at 6:32 AM, Carlos Alberto Lopez Perez > > <[email protected]> wrote: > >> I think the default build toolchain should be supported also, > >> at least without the requirement of "one year after the release". > >> > >> I propose this change to the policy over yours: > >> > >> - This policy applies to runtime dependencies to ensure smooth updates > >> for users. > >> - It does not apply to the build toolchain. > >> - A compiler other than the default compiler in an otherwise-supported > >> distribution may be required to build. > >> > >> + This policy applies to the runtime dependencies to ensure smooth > >> updates for users. > >> + The requirement of "one year after the release" does not apply to > >> the default toolchain. > >> + On that extra year of support a compiler other than the default one > >> in an otherwise-supported distribution may be required to build. > >> > >> > >> I think is important to not require a too much new version of the > >> default toolchain (GCC). > > > > Fine by me. > > > > Michael > > > > > > Ok. For the record: I just updated policy with this changes (plus a > minor clarification regarding that for the last version of a supported > distro both runtime and default toolchain dependencies are supported) > > > > _______________________________________________ > webkit-dev mailing list > [email protected] > https://lists.webkit.org/mailman/listinfo/webkit-dev > >
_______________________________________________ webkit-dev mailing list [email protected] https://lists.webkit.org/mailman/listinfo/webkit-dev
