I wasn’t aware that the build worked without a VS2010 pThreads build. I was running into issues because of the pThreads dll having embedded manifest problems earlier. Did you do anything special to circumvent that issue?
It won’t take much to switch it over but the problem was originally that I couldn’t get it to build without a newer compile of the pthreads library. Thus we were waiting for the pthreads folks to release a newer pthreads dll before doing the switch over. Also, I believe Brent Fulgham may have modified build-webkit to set environment variables appropriately because the VS2010 solution uses different ones than the VS2005 solution. I just have those variables set permanently and just build directly from the solution file. (Need to update those build.webkit.org instructions) On Apr 8, 2013, at 1:13 PM, Justin Haygood <justin.hayg...@reaktix.com> wrote: > What would it take to switch build-webkit, et al to the VS2010 build? (VS2010 > does work manually though, if you run build-webkit at least once, let it fail > since it can’t find VS2005/VS2008, and then build it from the solution file) > > From: webkit-dev-boun...@lists.webkit.org > [mailto:webkit-dev-boun...@lists.webkit.org] On Behalf Of Roger Fong > Sent: Monday, April 08, 2013 3:26 PM > To: Patrick Gansterer > Cc: WebKit Development > Subject: Re: [webkit-dev] Buildsystem cleanup > > Unfortunately this would cause a lot of complication in our internal build > setup that we currently don’t really have the resources to deal with right > now. > > It would be nice to unite all the build systems at some point in the future > but we’re going to push this one off for now. > > Also we’re planning on getting rid of the VS2005 eventually. > > On Apr 7, 2013, at 6:47 PM, Patrick Gansterer <par...@paroga.com> wrote: > > > Hi, > > since the Chromium code is getting removed step by step I think that the GYP > build system won't have a shiny future in the WebKit repository. In the GYP > vs. CMake match CMake gets an additional point: There is no WebKit port > working with GYP, but at least 3 with CMake. Accordantly to [1] GTK will give > CMake a try too. > Adopting the Mac port does not seam to be an easy task in the near future, > because of the very specific build requirements. > But what about the Windows ports? I updated the patch at [2] to work with a > more recent revision. Are there any chances to use CMake instead of the VS > solution files? At the moment it becomes even worst, since there are VS2005 > and VS2010 files in the tree, which duplicated many files. > The patch at [2] is only an initial example, since a complete implementation > would require more changes in the code. If CMake becomes an option, I'm > willing to provide an "complete" patch with all CMake files. > > -- Patrick > > [1] https://lists.webkit.org/pipermail/webkit-dev/2013-April/024399.html > [2] https://bugs.webkit.org/show_bug.cgi?id=72816 > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
