I was also wondering how the new requirements for svg and accelerated compositing affected the wince port.
Alex Christensen > On Jan 31, 2014, at 2:36 PM, Patrick Gansterer <[email protected]> wrote: > > On 31.01.2014, at 22:10, Anders Carlsson <[email protected]> wrote > >> looks like the last legitimate commit to the Windows CE port was on November >> 3rd November 2013, almost 3 months ago. > > What's the minimum upstream interval for downstream fixes to show ongoing > activity? > >> I also seem to remember that there’s no version of MSVC for Windows CE that >> can handle the C++11 features that we now use in WebKit. (Correct me if I’m >> wrong on this!) > > Windows Embedded Compact 2013 updated the compiler for CE. > >> With this in mind, does it make sense to keep the Windows CE port in the >> tree or should we remove it? > > Does it hurt somebody in the daily workflow? If yes, where exactly? > I'm still working on getting rid of WebKit/wince by merging it into > WebKit/win (with only a few #if WINCE) to reduce the impact of the WinCE > port, but it's hard if there is nobody who finds time for reviewing patches. > :-/ (e.g. webkit.org/b/119518 or webkit.org/b/123803 waiting for months - but > I don't want to blame somebody by this!) > > -- > Patrick > _______________________________________________ > 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
