I regularly build qtwebkit with VS2010 so the only real issue should be with project files. I did use the conversion wizard once on webkit/chromium and was able to build successfully with only a couple of minor tweaks.
I'd be happy to do the legwork on the VS2010 upgrade if it'd help. -Jake On Tue, Feb 1, 2011 at 7:31 AM, Adam Roben <[email protected]> wrote: > On Jan 31, 2011, at 9:04 PM, Jeremy Orlow wrote: > > How hard will the transition be? If it's going to take a lot of time and > cause a lot of churn anyway, would this be a good time to try and make that > port use GYP or CMake? (I assume the answer is probably no, but figured it > was worth asking anyway. :-) > > > VS2010 includes a project conversion wizard that can convert projects from > VS2005 (and presumably VS2008) format to VS2010. We've tried it previously > on WebKit and it seemed to work just fine with only minor issues. > > The goal of having fewer project files is a worthy one, however. Patrick > Gansterer offered to code up a patch to build Apple's Windows port using the > existing CMake build system, which will be very interesting to see! > > -Adam > > On Mon, Jan 31, 2011 at 12:46 PM, Adam Roben <[email protected]> wrote: > >> On Jan 31, 2011, at 3:41 PM, Peter Kasting wrote: >> >> On Mon, Jan 31, 2011 at 12:30 PM, Adam Roben <[email protected]> wrote: >> >>> Please let me (and the list) know if this change will cause you trouble, >>> and if there's something we can do to make the transition easier. >>> >> >> This may make life hard on Chromium as right now we don't support building >> with VS2010. We are working on adding support (I think >> http://crbug.com/25628 may be the closest bug). I'm not sure what time >> frame that will happen in. >> >> I don't think we have any plans to drop VS2005 support. If WebKit drops >> support it may force us to do so as well. >> >> In both cases above we're not so much impacted by vcproj/sln changes >> (since we use GYP to construct our vcproj and sln files) as we are by code >> changes, e.g. code that requires VS2010 to build correctly. >> >> >> I doubt that maintaining compatibility with VS2005's compiler would be an >> issue. As long as there's an EWS and/or buildbot to catch problems, we >> should be able to work around any compiler differences. I didn't mean to >> imply that we'd intentionally break compilation with VS2005's compiler; all >> I meant was that using VS2005 to build Apple's port would no longer be >> supported. >> >> -Adam >> >> >> _______________________________________________ >> webkit-dev mailing list >> [email protected] >> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev >> >> > > > _______________________________________________ > webkit-dev mailing list > [email protected] > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > >
_______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
