[webkit-dev] Building on Windows: WebKitSupportLibrary.zip is incomplete
Hi, all, I'm trying to build WebKit on Windows platform and getting some compilation errors like missing header files: pthread.h, unicode/uchar.h and others - for example, when building JavaScriptCore sub-project. When I manually open WebKit solution in VC++ 2005 Express and check JavaScriptCode properties, I see the following list of additional include directories: $(WebKitOutputDir)\obj\JavaScriptCore\$(ConfigurationName)\DerivedSources\ ../../ ../../os-win32/ ../../pcre/ ../../kjs/ ../../wtf/ $(WebKitLibrariesDir)\include $(WebKitLibrariesDir)\include\icu ../../../icu/include ../../bindings ../../bindings/c ../../bindings/jni $(WebKitOutputDir)\include\JavaScriptCore $(WebKitLibrariesDir)\include\pthreads In particular, pthreads.h, unicode/uchar.h, etc. are supposed to be in $(WebKitLibrariesDir) subdirs. This directory is generated by the perl script from the WebKitSupportLibrary.zip at the very beginning of the build process, before VCExpress.exe is launched. The problem is that WebKitSupportLibrary.zip archive *does not* contain the header files mentioned above. Is it a known problem with WebKit? Should I download anything else to build WebKit on Windows? Thanks, Artem ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Re: Automated tests (was: WebKit Project Goals)
On 26-Jul-07, at 14:00 , Darin Adler wrote: On Jul 26, 2007, at 10:42 AM, Andre-John Mas wrote: Are there any publicly available tools that we could use instead? I believe it would be of benefit to everyone if we were on the same page with the way we approaching testing. At the very least even if Apple uses a separate test process internally, it would be good if there were some universally available testing process that was part of the WebKit project. I agree. That would be great. We've had a hard time finding tools like what you describe, though. Any specific ideas? Can you do something to help with this? What should the requirements for the tool be, other than being freely available? Andre ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Building on Windows: WebKitSupportLibrary.zip is incomplete
Hi, Adam, indeed, I have missed this step. After running the update-webkit script (and passing some additional flags to curl to work via proxy), it seems all the required files are in WebKitLibraries directory. I will proceed with building WebKit. Thanks, Artem Adam Roben wrote: On Jul 26, 2007, at 12:15 AM, Artem Ananiev wrote: Hi, all, I'm trying to build WebKit on Windows platform and getting some compilation errors like missing header files: pthread.h, unicode/uchar.h and others - for example, when building JavaScriptCore sub-project. When I manually open WebKit solution in VC++ 2005 Express and check JavaScriptCode properties, I see the following list of additional include directories: $(WebKitOutputDir)\obj\JavaScriptCore\$(ConfigurationName)\DerivedSources\ ../../ ../../os-win32/ ../../pcre/ ../../kjs/ ../../wtf/ $(WebKitLibrariesDir)\include $(WebKitLibrariesDir)\include\icu ../../../icu/include ../../bindings ../../bindings/c ../../bindings/jni $(WebKitOutputDir)\include\JavaScriptCore $(WebKitLibrariesDir)\include\pthreads In particular, pthreads.h, unicode/uchar.h, etc. are supposed to be in $(WebKitLibrariesDir) subdirs. This directory is generated by the perl script from the WebKitSupportLibrary.zip at the very beginning of the build process, before VCExpress.exe is launched. The problem is that WebKitSupportLibrary.zip archive *does not* contain the header files mentioned above. Is it a known problem with WebKit? Should I download anything else to build WebKit on Windows? The headers you mentioned are actually part of a separate zip file that update-webkit downloads and extracts for you. Did you run the update-webkit script like http://webkit.org/building/checkout.html says? -Adam ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] compile safari in cygwin failed
I am using vc++ 2005 Express and did reinstall following the webkit instruction again, but still got the same error. Jerry Jerry K wrote: anyone can give some ideas about error MIDL 2272 faile? thanks interface IWebScriptObject : IUnknown interface IDOMObject : IWebScriptObject interface IDOMImplementation : IDOMObject 1oaidl.acf 1Processing C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include\ocidl.acf 1ocidl.acf 1..\Interfaces\IWebURLRequest.idl(80) : warning MIDL2039 : interface does not conform to [oleautomation] attribute : [ Parameter 'result' of Procedure 'allHTTPHeaderFields' ( Interface 'IWebURLRequest' ) ] 1..\Interfaces\IWebURLRequest.idl(90) : warning MIDL2039 : interface does not conform to [oleautomation] attribute : [ Parameter 'result' of Procedure 'HTTPBody' ( Interface 'IWebURLRequest' ) ] 1..\Interfaces\IWebURLRequest.idl(95) : warning MIDL2039 : interface does not conform to [oleautomation] attribute : [ Parameter 'result' of Procedure 'HTTPBodyStream' ( Interface 'IWebURLRequest' ) ] 1..\Interfaces\IWebScriptObject.idl(105) : warning MIDL2039 : interface does not conform to [oleautomation] attribute : [ Parameter 'args' of Procedure 'callWebScriptMethod' ( Interface 'IWebScriptObject' ) ] 1..\Interfaces\DOMCore.idl(81) : error MIDL2272 : interfaces must derive from another interface : [ Interface 'IDOMObject' ] 1..\Interfaces\DOMCore.idl(81) : error MIDL2011 : unresolved type declaration : IWebScriptObject [ Interface 'IDOMObject' ] 1..\Interfaces\DOMCore.idl(81) : warning MIDL2039 : interface does not conform to [oleautomation] attribute : [ Interface 'IDOMObject' ] 1..\Interfaces\DOMCore.idl(94) : error MIDL2011 : unresolved type declaration : IDOMObject [ Interface 'IDOMObject' ] 1midl : error MIDL9008 : internal compiler problem 0xc005 - the compiler cannot continue for an unknown reason. See documentation for suggestions on how to find a workaround. -- View this message in context: http://www.nabble.com/compile-safari-in-cygwin-fail-tf4120672.html#a11804973 Sent from the Webkit mailing list archive at Nabble.com. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Re: Automated tests (was: WebKit Project Goals)
On Jul 26, 2007, at 11:13 AM, Andre-John Mas wrote: What should the requirements for the tool be, other than being freely available? I'm not sure these are requirements, but here are some of the things I'd like to see: - representative of real world performance - one way to make it a real-world test is to use content from real-world websites, but that's the rub because the copyright owner may not give us license to use it as we wish - easy to run in an automated fashion so we can post results on the buildbots - easy to run with performance analysis tools - possible to run in non-WebKit browsers too - no axe to grind -- this wouldn't be a test specifically designed to highlight a particular performance problem - doesn't change a lot over time -- it's hard to judge changes in performance of the engine if the test is changing too There are other more subtle requirements. If we have too many different performance tests, they are no good because we can't run them all. If benchmarks are created by unaffiliated third parties, they are even more valuable because people won't assume they are slanted. -- Darin ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
