On Tuesday, June 26, 2012 03:26:35 PM ext Mülner, Helmut wrote: > > [...] > > The Qt 5 beta is getting closer, and I think we'll have something > > releasable within the next two weeks. Technically we have most things in > > place, but the sha1's in qt5.git will need to follow and get quite a bit > > closer to the HEADs of each repository. > > > > There's still a few technical gaps left (e.g. WebKit2 on Windows, some > > multimedia pieces on Mac and Windows, DnD on Mac), but I still think it's > > better to now ship a beta than to wait any longer. Please all make sure > > that you document these technical gaps in the Known Issues section of the > > release notes. > > [...] > > As far as I know there is NO WebKit available for Windows, at least if you > have to use VisualStudio2010. I tried to compile webkit after every update > for the several weeks now, and I always get unresolved references When > linking jsc, starting with: > > link /LIBPATH:"d:\Qt\qt5\qtbase\lib" /LIBPATH:"d:\Qt\qt5\qtbase\lib" /NOLOGO > /DYNAMICBASE /NXCOMPAT /DEBUG /SUBSYSTEM:CONSOLE > "/MANIFESTDEPENDENCY:type='win32' name='Microsoft.Windows.Common-Controls' > version='6.0.0.0' publicKeyToken='6595b64144ccf1df' language='*' > processorArchitecture='*'" /MANIFEST > /MANIFESTFILE:"obj/debug\jsc.intermediate.manifest" /OUT:..\bin\jsc.exe > @C:\Users\muh\AppData\Local\Temp\nmE341.tmp jsc.obj : error LNK2019: > unresolved external symbol __imp__WTFInvokeCrashHook referenced in function > "protected: void __thiscall JSC::JSUint8Array::finishCreation(class > JSC::JSGlobalData &)" > (?finishCreation@JSUint8Array@JSC@@IAEXAAVJSGlobalData@2@@Z) > > I suspect that these are just wrong dllexport/dllimport directives.
Yes. The status of WebKit on Windows is that an update is currently stuck in the queue for qt5.git :). It's a snapshot of trunk with three patches on top, two related to eliminating a pthreads dependency and the last one to fix the dllimport/export directives. I'm working on stabilizing the build right now (as you can see in commits in the qt5-module and trunk changes) and hope that we can get something decent for the beta. Simon _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
