Re: [webkit-dev] errors in Carbide but not on command line
Hi, The WebKit bld.inf contains the following lines: #ifndef __BROWSER_SDK #include domain/osextensions/platform_paths.hrh #endif This seems simple enough and, I can just remove the line '#include domain/osextensions/platform_paths.hrh'. However, in the JavaScriptCore bld.inf it looks likes this: /** Start horrible code extract */ #ifndef __BROWSER_SDK #include domain/osextensions/platform_paths.hrh ..\kjs\internal.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\internal.h) ..\kjs\interpreter.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\interpreter.h) ..\kjs\object.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\object.h) ..\kjs\protect.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\protect.h) ..\kjs\stdint.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\stdint.h) ..\bindings\npruntime.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\npruntime.h) ..\bindings\npruntime_impl.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\npruntime_impl.h) ..\bindings\npruntime_priv.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\npruntime_priv.h) ..\bindings\runtime.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\runtime.h) ..\bindings\runtime_object.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\runtime_object.h) ..\bindings\runtime_root.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\runtime_root.h) ..\bindings\NP_jsobject.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\NP_jsobject.h) ..\bindings\c\c_utility.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\c_utility.h) #else ..\kjs\internal.h \epoc32\include\oem\javascriptcore\internal.h ..\kjs\interpreter.h \epoc32\include\oem\javascriptcore\interpreter.h ..\kjs\object.h \epoc32\include\oem\javascriptcore\object.h ..\kjs\protect.h \epoc32\include\oem\javascriptcore\protect.h ..\kjs\stdint.h \epoc32\include\oem\javascriptcore\stdint.h ..\bindings\npruntime.h \epoc32\include\oem\javascriptcore\npruntime.h ..\bindings\npruntime_impl.h \epoc32\include\oem\javascriptcore\npruntime_impl.h ..\bindings\npruntime_priv.h \epoc32\include\oem\javascriptcore\npruntime_priv.h ..\bindings\runtime.h\epoc32\include\oem\javascriptcore\runtime.h ..\bindings\runtime_object.h \epoc32\include\oem\javascriptcore\runtime_object.h ..\bindings\runtime_root.h \epoc32\include\oem\javascriptcore\runtime_root.h ..\bindings\NP_jsobject.h \epoc32\include\oem\javascriptcore\NP_jsobject.h ..\bindings\c\c_utility.h \epoc32\include\oem\javascriptcore\c_utility.h #endif //#ifndef __BROWSER_SDK /** End horrible code extract */ So, presumably it's the first section that needs to go, but can all of it be removed, or just the offending line '#include domain/osextensions/platform_paths.hrh' ? On Wed, Jul 16, 2008 at 6:19 PM, Zalan Bujtas [EMAIL PROTECTED] wrote: #include domain/osextensions/platform_paths.hrh it is #ifdef-ed out in the bld.inf. Carbide does not manage #ifdefs in the build files properly. Zalan. On Wed, Jul 16, 2008 at 12:41 PM, Jack Wootton [EMAIL PROTECTED] wrote: To add, the following two files are displaying errors in Carbide: S60\JavaScriptCore\group\bld.inf S60\WebKit\group\bld.inf JavaScriptCore bld.inf both have a problem with the following line: #include domain/osextensions/platform_paths.hrh Presumably it can't find the file. On Wed, Jul 16, 2008 at 5:11 PM, Jack Wootton [EMAIL PROTECTED] wrote: Hi all, Having successfully built S60 WebKit on the command line (using an older version (21772 )), I decided to try building it in Carbide. I get the following errors: /** Start Errors **/ In file included from .\BLD.INF:50: .\.\JavaScriptCore\group\bld.inf:28: domain/osextensions/platform_paths.hrh: No such file or directory In file included from .\BLD.INF:52: .\.\WEBKIT\group\bld.inf:42: domain/osextensions/platform_paths.hrh: No such file or directory BLDMAKE ERROR: ERROR: cpp.exe returned non-zero exit status (8448) cpp.EXE -undef -nostdinc -+ -I ..\epoc32\include -I . -I .\ -I ..\epoc32\include\variant -include ..\epoc32\include\variant\Symbian_OS_v9.1.hrh .\BLD.INF /** End Errors **/ The build target inside Carbide was set to Emulator Debug (WINSCW). Can anyone help? -- Regards Jack -- Regards Jack ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev -- Regards Jack ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] errors in Carbide but not on command line
OK, So from reading this http://discussion.forum.nokia.com/forum/showthread.php?t=69737 I understand the situation better. One question: How can Nokia port the webkit so that it doesn't build in their own IDE? People moan about Google this and Google that, but this is something Google would never do. On Thu, Jul 17, 2008 at 9:50 AM, Jack Wootton [EMAIL PROTECTED] wrote: Hi, The WebKit bld.inf contains the following lines: #ifndef __BROWSER_SDK #include domain/osextensions/platform_paths.hrh #endif This seems simple enough and, I can just remove the line '#include domain/osextensions/platform_paths.hrh'. However, in the JavaScriptCore bld.inf it looks likes this: /** Start horrible code extract */ #ifndef __BROWSER_SDK #include domain/osextensions/platform_paths.hrh ..\kjs\internal.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\internal.h) ..\kjs\interpreter.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\interpreter.h) ..\kjs\object.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\object.h) ..\kjs\protect.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\protect.h) ..\kjs\stdint.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\stdint.h) ..\bindings\npruntime.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\npruntime.h) ..\bindings\npruntime_impl.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\npruntime_impl.h) ..\bindings\npruntime_priv.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\npruntime_priv.h) ..\bindings\runtime.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\runtime.h) ..\bindings\runtime_object.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\runtime_object.h) ..\bindings\runtime_root.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\runtime_root.h) ..\bindings\NP_jsobject.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\NP_jsobject.h) ..\bindings\c\c_utility.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\c_utility.h) #else ..\kjs\internal.h \epoc32\include\oem\javascriptcore\internal.h ..\kjs\interpreter.h \epoc32\include\oem\javascriptcore\interpreter.h ..\kjs\object.h \epoc32\include\oem\javascriptcore\object.h ..\kjs\protect.h \epoc32\include\oem\javascriptcore\protect.h ..\kjs\stdint.h \epoc32\include\oem\javascriptcore\stdint.h ..\bindings\npruntime.h \epoc32\include\oem\javascriptcore\npruntime.h ..\bindings\npruntime_impl.h \epoc32\include\oem\javascriptcore\npruntime_impl.h ..\bindings\npruntime_priv.h \epoc32\include\oem\javascriptcore\npruntime_priv.h ..\bindings\runtime.h\epoc32\include\oem\javascriptcore\runtime.h ..\bindings\runtime_object.h \epoc32\include\oem\javascriptcore\runtime_object.h ..\bindings\runtime_root.h \epoc32\include\oem\javascriptcore\runtime_root.h ..\bindings\NP_jsobject.h \epoc32\include\oem\javascriptcore\NP_jsobject.h ..\bindings\c\c_utility.h \epoc32\include\oem\javascriptcore\c_utility.h #endif //#ifndef __BROWSER_SDK /** End horrible code extract */ So, presumably it's the first section that needs to go, but can all of it be removed, or just the offending line '#include domain/osextensions/platform_paths.hrh' ? On Wed, Jul 16, 2008 at 6:19 PM, Zalan Bujtas [EMAIL PROTECTED] wrote: #include domain/osextensions/platform_paths.hrh it is #ifdef-ed out in the bld.inf. Carbide does not manage #ifdefs in the build files properly. Zalan. On Wed, Jul 16, 2008 at 12:41 PM, Jack Wootton [EMAIL PROTECTED] wrote: To add, the following two files are displaying errors in Carbide: S60\JavaScriptCore\group\bld.inf S60\WebKit\group\bld.inf JavaScriptCore bld.inf both have a problem with the following line: #include domain/osextensions/platform_paths.hrh Presumably it can't find the file. On Wed, Jul 16, 2008 at 5:11 PM, Jack Wootton [EMAIL PROTECTED] wrote: Hi all, Having successfully built S60 WebKit on the command line (using an older version (21772 )), I decided to try building it in Carbide. I get the following errors: /** Start Errors **/ In file included from .\BLD.INF:50: .\.\JavaScriptCore\group\bld.inf:28: domain/osextensions/platform_paths.hrh: No such file or directory In file included from .\BLD.INF:52: .\.\WEBKIT\group\bld.inf:42: domain/osextensions/platform_paths.hrh: No such file or directory BLDMAKE ERROR: ERROR: cpp.exe returned non-zero exit status (8448) cpp.EXE -undef -nostdinc -+ -I ..\epoc32\include -I . -I .\ -I ..\epoc32\include\variant -include ..\epoc32\include\variant\Symbian_OS_v9.1.hrh .\BLD.INF /** End Errors **/ The build target inside Carbide was set to Emulator Debug (WINSCW). Can anyone help? -- Regards Jack -- Regards Jack ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] errors in Carbide but not on command line
This seems simple enough and, I can just remove the line '#include domain/osextensions/platform_paths.hrh'. However, in the JavaScriptCore bld.inf it looks likes this: The targeted sdk (s60 3rd edition) cannot resolve MW_LAYER_SDK_EXPORT_PATH, so the export paths are hardcoded. That's the major difference between the #ifndef and the #else branch. I think you need to clean up the .inf files by removing the #ifndef __BROWSER_SDK' branch. How can Nokia port the webkit so that it doesn't build in their own IDE? I guess, Webkit was ported to S60 before, Carbide was taken into use and not been updated since. Zalan. On Thu, Jul 17, 2008 at 11:58 AM, Jack Wootton [EMAIL PROTECTED] wrote: Does anyone have a solution other than just commenting out all the files that shouldn't be included? This doesn't seem practical since there are around 60 errors reported from files not being found, it seems these files are meant to be conditionally included in the build process but that the '#ifndef __BROWSER_SDK' preprocessor commands are not working. On Thu, Jul 17, 2008 at 10:38 AM, Jack Wootton [EMAIL PROTECTED] wrote: OK, So from reading this http://discussion.forum.nokia.com/forum/showthread.php?t=69737 I understand the situation better. One question: How can Nokia port the webkit so that it doesn't build in their own IDE? People moan about Google this and Google that, but this is something Google would never do. On Thu, Jul 17, 2008 at 9:50 AM, Jack Wootton [EMAIL PROTECTED] wrote: Hi, The WebKit bld.inf contains the following lines: #ifndef __BROWSER_SDK #include domain/osextensions/platform_paths.hrh #endif This seems simple enough and, I can just remove the line '#include domain/osextensions/platform_paths.hrh'. However, in the JavaScriptCore bld.inf it looks likes this: /** Start horrible code extract */ #ifndef __BROWSER_SDK #include domain/osextensions/platform_paths.hrh ..\kjs\internal.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\internal.h) ..\kjs\interpreter.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\interpreter.h) ..\kjs\object.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\object.h) ..\kjs\protect.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\protect.h) ..\kjs\stdint.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\stdint.h) ..\bindings\npruntime.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\npruntime.h) ..\bindings\npruntime_impl.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\npruntime_impl.h) ..\bindings\npruntime_priv.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\npruntime_priv.h) ..\bindings\runtime.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\runtime.h) ..\bindings\runtime_object.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\runtime_object.h) ..\bindings\runtime_root.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\runtime_root.h) ..\bindings\NP_jsobject.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\NP_jsobject.h) ..\bindings\c\c_utility.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\c_utility.h) #else ..\kjs\internal.h \epoc32\include\oem\javascriptcore\internal.h ..\kjs\interpreter.h \epoc32\include\oem\javascriptcore\interpreter.h ..\kjs\object.h \epoc32\include\oem\javascriptcore\object.h ..\kjs\protect.h \epoc32\include\oem\javascriptcore\protect.h ..\kjs\stdint.h \epoc32\include\oem\javascriptcore\stdint.h ..\bindings\npruntime.h \epoc32\include\oem\javascriptcore\npruntime.h ..\bindings\npruntime_impl.h \epoc32\include\oem\javascriptcore\npruntime_impl.h ..\bindings\npruntime_priv.h \epoc32\include\oem\javascriptcore\npruntime_priv.h ..\bindings\runtime.h \epoc32\include\oem\javascriptcore\runtime.h ..\bindings\runtime_object.h \epoc32\include\oem\javascriptcore\runtime_object.h ..\bindings\runtime_root.h \epoc32\include\oem\javascriptcore\runtime_root.h ..\bindings\NP_jsobject.h \epoc32\include\oem\javascriptcore\NP_jsobject.h ..\bindings\c\c_utility.h \epoc32\include\oem\javascriptcore\c_utility.h #endif //#ifndef __BROWSER_SDK /** End horrible code extract */ So, presumably it's the first section that needs to go, but can all of it be removed, or just the offending line '#include domain/osextensions/platform_paths.hrh' ? On Wed, Jul 16, 2008 at 6:19 PM, Zalan Bujtas [EMAIL PROTECTED] wrote: #include domain/osextensions/platform_paths.hrh it is #ifdef-ed out in the bld.inf. Carbide does not manage #ifdefs in the build files properly. Zalan. On Wed, Jul 16, 2008 at 12:41 PM, Jack Wootton [EMAIL PROTECTED] wrote: To add, the following two files are displaying errors in Carbide: S60\JavaScriptCore\group\bld.inf S60\WebKit\group\bld.inf JavaScriptCore bld.inf both have a problem with the following line: #include domain/osextensions/platform_paths.hrh Presumably it can't find the file. On Wed, Jul 16, 2008 at 5:11 PM, Jack Wootton [EMAIL PROTECTED] wrote: Hi
Re: [webkit-dev] errors in Carbide but not on command line
Have you tried instructions from: http://wiki.forum.nokia.com/index.php/Building_S60Webkit And yes, using CodeWarrior might also solve those bld.inf problems, as most likely initial port was done before Carbide was taken into use. Regards, Jonni -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ext Zalan Bujtas Sent: 17 July, 2008 13:35 To: Jack Wootton Cc: webkit-dev@lists.webkit.org Subject: Re: [webkit-dev] errors in Carbide but not on command line This seems simple enough and, I can just remove the line '#include domain/osextensions/platform_paths.hrh'. However, in the JavaScriptCore bld.inf it looks likes this: The targeted sdk (s60 3rd edition) cannot resolve MW_LAYER_SDK_EXPORT_PATH, so the export paths are hardcoded. That's the major difference between the #ifndef and the #else branch. I think you need to clean up the .inf files by removing the #ifndef __BROWSER_SDK' branch. How can Nokia port the webkit so that it doesn't build in their own IDE? I guess, Webkit was ported to S60 before, Carbide was taken into use and not been updated since. Zalan. On Thu, Jul 17, 2008 at 11:58 AM, Jack Wootton [EMAIL PROTECTED] wrote: Does anyone have a solution other than just commenting out all the files that shouldn't be included? This doesn't seem practical since there are around 60 errors reported from files not being found, it seems these files are meant to be conditionally included in the build process but that the '#ifndef __BROWSER_SDK' preprocessor commands are not working. On Thu, Jul 17, 2008 at 10:38 AM, Jack Wootton [EMAIL PROTECTED] wrote: OK, So from reading this http://discussion.forum.nokia.com/forum/showthread.php?t=69737 I understand the situation better. One question: How can Nokia port the webkit so that it doesn't build in their own IDE? People moan about Google this and Google that, but this is something Google would never do. On Thu, Jul 17, 2008 at 9:50 AM, Jack Wootton [EMAIL PROTECTED] wrote: Hi, The WebKit bld.inf contains the following lines: #ifndef __BROWSER_SDK #include domain/osextensions/platform_paths.hrh #endif This seems simple enough and, I can just remove the line '#include domain/osextensions/platform_paths.hrh'. However, in the JavaScriptCore bld.inf it looks likes this: /** Start horrible code extract */ #ifndef __BROWSER_SDK #include domain/osextensions/platform_paths.hrh ..\kjs\internal.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\internal.h) ..\kjs\interpreter.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\interpreter.h) ..\kjs\object.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\object.h) ..\kjs\protect.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\protect.h) ..\kjs\stdint.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\stdint.h) ..\bindings\npruntime.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\npruntime.h) ..\bindings\npruntime_impl.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\npruntime_impl.h) ..\bindings\npruntime_priv.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\npruntime_priv.h) ..\bindings\runtime.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\runtime.h) ..\bindings\runtime_object.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\runtime_object.h) ..\bindings\runtime_root.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\runtime_root.h) ..\bindings\NP_jsobject.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\NP_jsobject.h) ..\bindings\c\c_utility.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\c_utility.h) #else ..\kjs\internal.h \epoc32\include\oem\javascriptcore\internal.h ..\kjs\interpreter.h \epoc32\include\oem\javascriptcore\interpreter.h ..\kjs\object.h \epoc32\include\oem\javascriptcore\object.h ..\kjs\protect.h \epoc32\include\oem\javascriptcore\protect.h ..\kjs\stdint.h \epoc32\include\oem\javascriptcore\stdint.h ..\bindings\npruntime.h \epoc32\include\oem\javascriptcore\npruntime.h ..\bindings\npruntime_impl.h \epoc32\include\oem\javascriptcore\npruntime_impl.h ..\bindings\npruntime_priv.h \epoc32\include\oem\javascriptcore\npruntime_priv.h ..\bindings\runtime.h \epoc32\include\oem\javascriptcore\runtime.h ..\bindings\runtime_object.h \epoc32\include\oem\javascriptcore\runtime_object.h ..\bindings\runtime_root.h \epoc32\include\oem\javascriptcore\runtime_root.h ..\bindings\NP_jsobject.h \epoc32\include\oem\javascriptcore\NP_jsobject.h ..\bindings\c\c_utility.h \epoc32\include\oem\javascriptcore\c_utility.h #endif //#ifndef __BROWSER_SDK /** End horrible code extract */ So, presumably it's the first section that needs to go, but can all of it be removed, or just the offending line '#include domain/osextensions/platform_paths.hrh' ? On Wed, Jul 16, 2008 at 6:19 PM, Zalan Bujtas [EMAIL PROTECTED] wrote: #include domain/osextensions/platform_paths.hrh it is
Re: [webkit-dev] errors in Carbide but not on command line
Hi Jonni, Yes, I followed those instructions, although instruction 3 doesn't actually request that anything be done. So I just left it. I can't change IDEs so what can I do, other just commenting out all the files...which then means I can't build on the command line if I need to. As I side issue: The instructions found here: http://trac.webkit.org/wiki/S60Webkit do not match the instructions found here http://wiki.forum.nokia.com/index.php/Building_S60Webkit. There is no mention of having to edit the build.bat file. In fact the instructions at http://trac.webkit.org/wiki/S60Webkit seem to be out of date. While I'm trying to actually build webkit s60, I thought I'd get to grips with the source code: Where can I find the documentation for webkit s60? All I can find is the source code :P Cheers, Jack On Thu, Jul 17, 2008 at 11:39 AM, [EMAIL PROTECTED] wrote: Have you tried instructions from: http://wiki.forum.nokia.com/index.php/Building_S60Webkit And yes, using CodeWarrior might also solve those bld.inf problems, as most likely initial port was done before Carbide was taken into use. Regards, Jonni -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ext Zalan Bujtas Sent: 17 July, 2008 13:35 To: Jack Wootton Cc: webkit-dev@lists.webkit.org Subject: Re: [webkit-dev] errors in Carbide but not on command line This seems simple enough and, I can just remove the line '#include domain/osextensions/platform_paths.hrh'. However, in the JavaScriptCore bld.inf it looks likes this: The targeted sdk (s60 3rd edition) cannot resolve MW_LAYER_SDK_EXPORT_PATH, so the export paths are hardcoded. That's the major difference between the #ifndef and the #else branch. I think you need to clean up the .inf files by removing the #ifndef __BROWSER_SDK' branch. How can Nokia port the webkit so that it doesn't build in their own IDE? I guess, Webkit was ported to S60 before, Carbide was taken into use and not been updated since. Zalan. On Thu, Jul 17, 2008 at 11:58 AM, Jack Wootton [EMAIL PROTECTED] wrote: Does anyone have a solution other than just commenting out all the files that shouldn't be included? This doesn't seem practical since there are around 60 errors reported from files not being found, it seems these files are meant to be conditionally included in the build process but that the '#ifndef __BROWSER_SDK' preprocessor commands are not working. On Thu, Jul 17, 2008 at 10:38 AM, Jack Wootton [EMAIL PROTECTED] wrote: OK, So from reading this http://discussion.forum.nokia.com/forum/showthread.php?t=69737 I understand the situation better. One question: How can Nokia port the webkit so that it doesn't build in their own IDE? People moan about Google this and Google that, but this is something Google would never do. On Thu, Jul 17, 2008 at 9:50 AM, Jack Wootton [EMAIL PROTECTED] wrote: Hi, The WebKit bld.inf contains the following lines: #ifndef __BROWSER_SDK #include domain/osextensions/platform_paths.hrh #endif This seems simple enough and, I can just remove the line '#include domain/osextensions/platform_paths.hrh'. However, in the JavaScriptCore bld.inf it looks likes this: /** Start horrible code extract */ #ifndef __BROWSER_SDK #include domain/osextensions/platform_paths.hrh ..\kjs\internal.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\internal.h) ..\kjs\interpreter.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\interpreter.h) ..\kjs\object.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\object.h) ..\kjs\protect.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\protect.h) ..\kjs\stdint.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\stdint.h) ..\bindings\npruntime.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\npruntime.h) ..\bindings\npruntime_impl.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\npruntime_impl.h) ..\bindings\npruntime_priv.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\npruntime_priv.h) ..\bindings\runtime.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\runtime.h) ..\bindings\runtime_object.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\runtime_object.h) ..\bindings\runtime_root.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\runtime_root.h) ..\bindings\NP_jsobject.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\NP_jsobject.h) ..\bindings\c\c_utility.h MW_LAYER_SDK_EXPORT_PATH(javascriptcore\c_utility.h) #else ..\kjs\internal.h \epoc32\include\oem\javascriptcore\internal.h ..\kjs\interpreter.h \epoc32\include\oem\javascriptcore\interpreter.h ..\kjs\object.h \epoc32\include\oem\javascriptcore\object.h ..\kjs\protect.h \epoc32\include\oem\javascriptcore\protect.h ..\kjs\stdint.h \epoc32\include\oem\javascriptcore\stdint.h ..\bindings\npruntime.h \epoc32\include\oem\javascriptcore\npruntime.h ..\bindings\npruntime_impl.h \epoc32\include\oem\javascriptcore\npruntime_impl.h ..\bindings\npruntime_priv.h \epoc32\include\oem\javascriptcore\npruntime_priv.h ..\bindings\runtime.h
[webkit-dev] Questions about WebKit Platform/Toolkit abstraction layer
Hi, I am a beginner of WebKit, and I've tried to find the documents about WebKit's Platform/Toolkit abstraction layer(API), but i found nothing. What i mean is that like Qt port of WebKit, i think the architecture as below: Qt API: like QWebPage, QWebFrame, QWebSetting, etc. == Platform abstraction layer == WebKit - WebCore - JavaScript Core == Toolkit abstraction layer == Qt core module I would like to ask, where can I find WebKit Platform/Toolkit abstraction layer of relevant information? Or I just can find what I need by tracing the WebKit source code? What I have to do is to port WebKit onto a proprietry embedded platform So that I have to find document about abstraction layer, just like APIs supported by pure WebKit Why I say pure WebKit because in WebKit's source code, I saw the Mac port, Qt port, Gtk port, but I didn't know where to begin using WebKit... (Or not so-called pure WebKit?) If there are WebKit porting example, or any relevant information, that's also helpful to me! If there is something incorrect, please let me know. Thanks! Best Regards Belay ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Translucent (i)frames support
The bug on Mac at least is just that NSScrollViews blit when scrolling, and they know nothing about transparency layers. Our solution to similar problems has been to just disable blitting in these cases and do slow repainting when scrolling happens. Because there is *no cache* of transparency layer contents, we are unable to do a blit directly within the transparency layer itself, so a slow redraw is the only option. Moving to a model where we cache bitmaps for transparency layers is possible but potentially wasteful memory- wise given the way CSS opacity is designed. dave On Jul 17, 2008, at 9:36 AM, Artem Ananiev wrote: Hi, webkit developers, I have recently faced a problem with support for translucent (i)frames in our (java) port, and tried to find how other ports (gtk, win, mac) deal with the same issue. The test is short (launch the test and try to scroll inner frames): html body div style=opacity:0.5;position:absolute;left:150;top:150 iframe src=http://java.sun.com/javase/6/docs/api; width=600 height=450/iframe /div div style=opacity:0.2;position:absolute;left:250;top:250 iframe src=http://java.sun.com/javase/6/docs/api; width=600 height=450/iframe /div /body /html I was very surprised when found no webkit ports displayed the page correctly! I tried Safari 3.1 on Mac and Win and GTK Launcher on Linux (haven't looked at Safari 4.0, though). The only browser which 'passed' the test was Firefox: all the frames were displayed correctly and scrolled smoothly. It seems that both mac/win and gtk ports use some caches for rendered pages, however some bugs exist in the implementations. In Java port we have two different approaches for rendering: one is fast, but without any support of translucent (i)frames, another is correct (even with the test above), but slow. The second one is a kind of experimental, and what I want to do is to speed it up (by using some rendering cache) and make it default. The next two days I spent trying to implement the correct rendering cache. The idea is simple: render all the frames separately from each other to different offscreen images, and composite them to get a final image on the screen. However, I failed with this task :( The first part is simple: to render the frame contents I call Frame::paint(gc, rect) and skip all subsequent Widget::paint(gc, rect) calls. That's fine. The second part - compositing - is somewhat I couldn't implement. The problem is there is no way (or I don't know this way) for a given Frame to render all its child frames without rendering the frame itself. In other words, I have to render some part of the frame twice: first, all the dirty regions into the cache, and second, all the frame to get children painted correctly. Any ideas? Thanks, Artem ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] QtLauncher -- acid3 crashes (doesn't happen with Gtk).
Hi, Anyone else having issues with acid3 with Qt. It crashes as a release build; as a debug build it finishes but failes the link test. Sometimes the release build failes at 74/100 -- other times at 94/100. Build from the same source GtkLauncher passes 100/100. I currently have r35189 and will update to the latest and test again; but wanted to make folks aware. (btw. this is on RedHat Enterprise Linux 5.1client with gcc 4.1.2 compiled in x86_64). I've seen the following backtrace with gdb: #0 0x2b444763 in WebCore::JSDocument::getValueProperty () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #1 0x2ad9a49b in KJS::Machine::privateExecute () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #2 0x2ada15bf in KJS::Machine::execute () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #3 0x2adc6793 in KJS::JSFunction::call () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #4 0x2ae44748 in WebCore::ScheduledAction::execute () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #5 0x2ae2178a in WebCore::JSDOMWindowBase::timerFired () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #6 0x2ae218ac in WebCore::DOMWindowTimer::fired () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #7 0x2b11a4e3 in WebCore::TimerBase::fireTimers () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #8 0x2b11a7b7 in WebCore::TimerBase::sharedTimerFired () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #9 0x2b562c9f in WebCore::SharedTimerQt::qt_metacall () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #10 0x2c9d3a7b in QMetaObject::activate (sender=0x11ff3aa0, from_signal_index=value optimized out, to_signal_index=4, argv=0x2f9b3a00) at kernel/qobject.cpp:3001 #11 0x2c9cf1ba in QObject::event (this=0x11ff3aa0, e=0x7fff3d6669d0) at kernel/qobject.cpp:1096 #12 0x2befba1f in QApplicationPrivate::notify_helper (this=0x11fe7420, receiver=0x11ff3aa0, e=0x7fff3d667400) at kernel/qapplication.cpp:3772 #13 0x2bf0064e in QApplication::notify (this=0x7fff3d6676f0, receiver=0x11ff3aa0, e=0x7fff3d667400) at kernel/qapplication.cpp:3739 #14 0x2c9bfb29 in QCoreApplication::notifyInternal (this=0x7fff3d6676f0, receiver=0x11ff3aa0, event=0x7fff3d667400) at kernel/qcoreapplication.cpp:587 #15 0x2c9ea487 in QTimerInfoList::activateTimers (this=0x11ff3910) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #16 0x2c9e7fed in timerSourceDispatch (source=value optimized out) at kernel/qeventdispatcher_glib.cpp:166 #17 0x003ba402cf44 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #18 0x003ba402fd7d in g_main_context_check () from /lib64/libglib-2.0.so.0 #19 0x003ba40302ae in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #20 0x2c9e842e in QEventDispatcherGlib::processEvents (this=0x11ff0470, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:325 #21 0x2bf8171f in QGuiEventDispatcherGlib::processEvents (this=0x2f9b3a00, flags=value optimized out) at kernel/qguieventdispatcher_glib.cpp:204 #22 0x2c9bef45 in QEventLoop::processEvents (this=value optimized out, [EMAIL PROTECTED]) at kernel/qeventloop.cpp:149 #23 0x2c9bf0aa in QEventLoop::exec (this=0x7fff3d667650, [EMAIL PROTECTED]) at kernel/qeventloop.cpp:200 #24 0x2c9c10f9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845 #25 0x00411f39 in main () -- #0 0x2adf86bb in KJS::PropertyMap::put () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #1 0x2b513997 in WebCore::JSSVGLength::getConstructor () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #2 0x2b4bef8e in WebCore::JSDOMWindow::getValueProperty () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #3 0x2ad98c39 in KJS::resolve_skip () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #4 0x2ad9a305 in KJS::Machine::privateExecute () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #5 0x2ada15bf in KJS::Machine::execute () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #6 0x2adc6793 in KJS::JSFunction::call () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #7 0x2ae44748 in WebCore::ScheduledAction::execute () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #8 0x2ae2178a in WebCore::JSDOMWindowBase::timerFired () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #9 0x2ae218ac in WebCore::DOMWindowTimer::fired () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #10
Re: [webkit-dev] How to use webkit ?
Hi, On Thu, Jul 17, 2008 at 12:57 PM, Nemix [EMAIL PROTECTED] wrote: Hmm I haven't Mac OS, I have Windows and can't develop on Mac at the moment (... and maybe never for this project ...). And XCode seems not to be available for Windows. I'm a little confused by your requirements (perhaps this is just a language issue?) I thought you had originally said you were targeting Mac OS X and the iPhone for your software. If so, I'm confused why you are wishing to do the development on Windows. So, let's assume I misunderstood, and you wish to develop something to run on Windows, OS X, and the iPhone. In this case, your best bet (as of today) is probably to investigate the Qt tool chain. I believe this is somewhat expensive (~ $3,500 per seat IIRC), but certainly a good deal if you wish to deploy simultaneously on multiple platforms. WebKit is not currently available for use on Windows with an Objective-C interface. No one (to my knowledge) has built it using GNUstep or a similar Objective C infrastructure. As far as I know, Apple itself builds Safari on Windows using C++ and COM calls to interact with WebKit. You might look into the Cocotron project, which supposedly provides a way to build applications on Mac OS X and deploy them on Windows, but I don't think it's a polished distribution ready for end-user development. If I develop my application for iPhone thanks to documents, tools and videos on this page : http://developer.apple.com/iphone/ Will my web application run for Mac OS at 100% ? I am not sure about the answer... so I prefer to ask a confirmation ;) The iPhone SDK is current under NDA, so details can't be discussed. However, I think it is safe to say that (even if it was possible) to take an iPhone application and plunk it down on a Mac OS desktop to run it, you would probably not end up with a good user interaction. Consider that the iPhone doesn't seem to provide a means to cut/paste between applications, storage seems to be sandboxed so applications can't see each other's data, etc. Most users expect to be able to pass data to and from programs on the desktop. Having a Cocoa application is probably a good first step to getting something running on the iPhone, but I don't think it's realistic to hope to build one binary and run it in both places. -Brent ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] How to use webkit ?
Hi Nemix, You need a Mac to do iPhone development. Go ask your boss for a nice MacBook Pro laptop or a Mac Pro tower. Don't skimp on RAM, either. :) http://store.apple.com/ Dave On Thu, 7/17/08, Nemix [EMAIL PROTECTED] wrote: Hi ^^ After a discussion with my boss, I have to study a little more webkit solution. So I looked for webkit solution again since yesterday. Dave, you said : I'm not sure how well Eclipse supports Objective-C. I'd recommend using Xcode, which is the free IDE available for Mac OS X. Hmm I haven't Mac OS, I have Windows and can't develop on Mac at the moment (... and maybe never for this project ...). And XCode seems not to be available for Windows. So I search for something to develop with webkit and Objective-C on Windows. I have had a look on Apple website as Brent said. But they talk about XCode and nothing else (I haven't seen something else but maybe have I forgotten something ^^). I have seen : It is also possible to write Objective-C Cocoa programs in a simple text editor and build it manually with GCC or GNUstep's makefile scripts. http://en.wikipedia.org/wiki/Cocoa_(software) Does it work in my case ? I prefer to develop on a software... Do you know an other solution ? If I develop my application for iPhone thanks to documents, tools and videos on this page : http://developer.apple.com/iphone/ Will my web application run for Mac OS at 100% ? I am not sure about the answer... so I prefer to ask a confirmation ;) Thank you very much ! ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] QtLauncher -- acid3 crashes (doesn't happen with Gtk).
Quick update -- with r35223 it now also happens with a debug build. Investigating... - Jacob -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Refstrup, Jacob Grundtvig Sent: Thursday, July 17, 2008 11:44 AM To: webkit-dev@lists.webkit.org Subject: [webkit-dev] QtLauncher -- acid3 crashes (doesn't happen with Gtk). Hi, Anyone else having issues with acid3 with Qt. It crashes as a release build; as a debug build it finishes but failes the link test. Sometimes the release build failes at 74/100 -- other times at 94/100. Build from the same source GtkLauncher passes 100/100. I currently have r35189 and will update to the latest and test again; but wanted to make folks aware. (btw. this is on RedHat Enterprise Linux 5.1client with gcc 4.1.2 compiled in x86_64). I've seen the following backtrace with gdb: #0 0x2b444763 in WebCore::JSDocument::getValueProperty () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #1 0x2ad9a49b in KJS::Machine::privateExecute () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #2 0x2ada15bf in KJS::Machine::execute () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #3 0x2adc6793 in KJS::JSFunction::call () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #4 0x2ae44748 in WebCore::ScheduledAction::execute () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #5 0x2ae2178a in WebCore::JSDOMWindowBase::timerFired () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #6 0x2ae218ac in WebCore::DOMWindowTimer::fired () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #7 0x2b11a4e3 in WebCore::TimerBase::fireTimers () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #8 0x2b11a7b7 in WebCore::TimerBase::sharedTimerFired () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #9 0x2b562c9f in WebCore::SharedTimerQt::qt_metacall () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #10 0x2c9d3a7b in QMetaObject::activate (sender=0x11ff3aa0, from_signal_index=value optimized out, to_signal_index=4, argv=0x2f9b3a00) at kernel/qobject.cpp:3001 #11 0x2c9cf1ba in QObject::event (this=0x11ff3aa0, e=0x7fff3d6669d0) at kernel/qobject.cpp:1096 #12 0x2befba1f in QApplicationPrivate::notify_helper (this=0x11fe7420, receiver=0x11ff3aa0, e=0x7fff3d667400) at kernel/qapplication.cpp:3772 #13 0x2bf0064e in QApplication::notify (this=0x7fff3d6676f0, receiver=0x11ff3aa0, e=0x7fff3d667400) at kernel/qapplication.cpp:3739 #14 0x2c9bfb29 in QCoreApplication::notifyInternal (this=0x7fff3d6676f0, receiver=0x11ff3aa0, event=0x7fff3d667400) at kernel/qcoreapplication.cpp:587 #15 0x2c9ea487 in QTimerInfoList::activateTimers (this=0x11ff3910) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #16 0x2c9e7fed in timerSourceDispatch (source=value optimized out) at kernel/qeventdispatcher_glib.cpp:166 #17 0x003ba402cf44 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #18 0x003ba402fd7d in g_main_context_check () from /lib64/libglib-2.0.so.0 #19 0x003ba40302ae in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #20 0x2c9e842e in QEventDispatcherGlib::processEvents (this=0x11ff0470, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:325 #21 0x2bf8171f in QGuiEventDispatcherGlib::processEvents (this=0x2f9b3a00, flags=value optimized out) at kernel/qguieventdispatcher_glib.cpp:204 #22 0x2c9bef45 in QEventLoop::processEvents (this=value optimized out, [EMAIL PROTECTED]) at kernel/qeventloop.cpp:149 #23 0x2c9bf0aa in QEventLoop::exec (this=0x7fff3d667650, [EMAIL PROTECTED]) at kernel/qeventloop.cpp:200 #24 0x2c9c10f9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845 #25 0x00411f39 in main () -- #0 0x2adf86bb in KJS::PropertyMap::put () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #1 0x2b513997 in WebCore::JSSVGLength::getConstructor () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #2 0x2b4bef8e in WebCore::JSDOMWindow::getValueProperty () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #3 0x2ad98c39 in KJS::resolve_skip () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #4 0x2ad9a305 in KJS::Machine::privateExecute () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #5 0x2ada15bf in KJS::Machine::execute () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #6 0x2adc6793 in KJS::JSFunction::call () from
Re: [webkit-dev] QtLauncher -- acid3 crashes (doesn't happen with Gtk).
After a few VERY clean builds both Qt release/debug now behaves the same and gets to 96/100. - Jacob -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Refstrup, Jacob Grundtvig Sent: Thursday, July 17, 2008 2:14 PM To: webkit-dev@lists.webkit.org Subject: Re: [webkit-dev] QtLauncher -- acid3 crashes (doesn't happen with Gtk). Quick update -- with r35223 it now also happens with a debug build. Investigating... - Jacob -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Refstrup, Jacob Grundtvig Sent: Thursday, July 17, 2008 11:44 AM To: webkit-dev@lists.webkit.org Subject: [webkit-dev] QtLauncher -- acid3 crashes (doesn't happen with Gtk). Hi, Anyone else having issues with acid3 with Qt. It crashes as a release build; as a debug build it finishes but failes the link test. Sometimes the release build failes at 74/100 -- other times at 94/100. Build from the same source GtkLauncher passes 100/100. I currently have r35189 and will update to the latest and test again; but wanted to make folks aware. (btw. this is on RedHat Enterprise Linux 5.1client with gcc 4.1.2 compiled in x86_64). I've seen the following backtrace with gdb: #0 0x2b444763 in WebCore::JSDocument::getValueProperty () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #1 0x2ad9a49b in KJS::Machine::privateExecute () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #2 0x2ada15bf in KJS::Machine::execute () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #3 0x2adc6793 in KJS::JSFunction::call () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #4 0x2ae44748 in WebCore::ScheduledAction::execute () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #5 0x2ae2178a in WebCore::JSDOMWindowBase::timerFired () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #6 0x2ae218ac in WebCore::DOMWindowTimer::fired () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #7 0x2b11a4e3 in WebCore::TimerBase::fireTimers () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #8 0x2b11a7b7 in WebCore::TimerBase::sharedTimerFired () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #9 0x2b562c9f in WebCore::SharedTimerQt::qt_metacall () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #10 0x2c9d3a7b in QMetaObject::activate (sender=0x11ff3aa0, from_signal_index=value optimized out, to_signal_index=4, argv=0x2f9b3a00) at kernel/qobject.cpp:3001 #11 0x2c9cf1ba in QObject::event (this=0x11ff3aa0, e=0x7fff3d6669d0) at kernel/qobject.cpp:1096 #12 0x2befba1f in QApplicationPrivate::notify_helper (this=0x11fe7420, receiver=0x11ff3aa0, e=0x7fff3d667400) at kernel/qapplication.cpp:3772 #13 0x2bf0064e in QApplication::notify (this=0x7fff3d6676f0, receiver=0x11ff3aa0, e=0x7fff3d667400) at kernel/qapplication.cpp:3739 #14 0x2c9bfb29 in QCoreApplication::notifyInternal (this=0x7fff3d6676f0, receiver=0x11ff3aa0, event=0x7fff3d667400) at kernel/qcoreapplication.cpp:587 #15 0x2c9ea487 in QTimerInfoList::activateTimers (this=0x11ff3910) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #16 0x2c9e7fed in timerSourceDispatch (source=value optimized out) at kernel/qeventdispatcher_glib.cpp:166 #17 0x003ba402cf44 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #18 0x003ba402fd7d in g_main_context_check () from /lib64/libglib-2.0.so.0 #19 0x003ba40302ae in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #20 0x2c9e842e in QEventDispatcherGlib::processEvents (this=0x11ff0470, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:325 #21 0x2bf8171f in QGuiEventDispatcherGlib::processEvents (this=0x2f9b3a00, flags=value optimized out) at kernel/qguieventdispatcher_glib.cpp:204 #22 0x2c9bef45 in QEventLoop::processEvents (this=value optimized out, [EMAIL PROTECTED]) at kernel/qeventloop.cpp:149 #23 0x2c9bf0aa in QEventLoop::exec (this=0x7fff3d667650, [EMAIL PROTECTED]) at kernel/qeventloop.cpp:200 #24 0x2c9c10f9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845 #25 0x00411f39 in main () -- #0 0x2adf86bb in KJS::PropertyMap::put () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #1 0x2b513997 in WebCore::JSSVGLength::getConstructor () from /work/jrefstru/webkit/WebKitBuild/Release/lib/libQtWebKit.so.4 #2 0x2b4bef8e in WebCore::JSDOMWindow::getValueProperty () from
[webkit-dev] Building WebKit on Visual Studio 2005 is failed!
Dear all, I am building the WebKit on Visual Studio 2005. I used the latest source by 'update-webkit' script. I installed the cygwin with cygwin-downloader on webkit.org. perl version is v5.10. gpref is properly installed as well. but I have a few error messages. One of messages is ' ' ' # Lower case all the values, as CSS values are case-insensitive perl -ne 'print lc' /home/JC47~1.PAR/WebKit/WebCore/css/CSSValueKeywords.in /home/JC47~1.PAR/WebKit/WebCore/css/SVGCSSValueKeywords.in CSSValueKeywords.in gperf -CDEot -L ANSI-C -k '*' -N findColor -D -s 2 /home/JC47~1.PAR/WebKit/WebCore/platform/ColorData.gperf ColorData.c if sort CSSValueKeywords.in | uniq -d | grep -E '^[^#]'; then echo 'Duplicate value!'; exit 1; fi gperf -CEot -L ANSI-C -k * -N findDoctypeEntry -F ,PubIDInfo::eAlmostStandards,PubIDInfo::eAlmostStandards /home/JC47~1.PAR/WebKit/WebCore/html/DocTypeStrings.gperf DocTypeStrings.cpp Duplicate value! make: *** [CSSValueKeywords.h] Error 1 make: *** Waiting for unfinished jobs make: Nothing to be done for `all'. ' ' ' 'CSSValueKeywords.h' is not generated. Have you seen this message before? Thanks in advance. :) JC Park. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
