[webkit-dev] Target Compilation problem in S60Webkit R21772
Gurpreet Singh
singhgupi at gmail.com
Mon Jul 30 05:04:17 PDT 2007
Hi,
My environment is
S60 Webkit trunk (r21772), S60_3rd SDK, Carbide.c++ 1.2 Express
I compiled webkit/reindeer and it runs fine in the emulator.
But compilation on target is a big problem. Even there is an open Bug for
that.
But is there somebody(some angel), who has successfully compiled S60 Webkit
on target.
I mean, copiled, downloaded and run on Target. After weeks of efforts, I'm
able to compile and download on my N80, but Reindeer doesn't run. I gives so
many error.
Any kind of help is appreciated.
Thanks!!!
Br
Gurpreet
singhgupi at gmail.com
www.mobisy.com
On 7/30/07, webkit-dev-request at lists.webkit.org <
webkit-dev-request at lists.webkit.org> wrote:
>
> Send webkit-dev mailing list submissions to
> webkit-dev at lists.webkit.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.webkit.org/mailman/listinfo/webkit-dev
> or, via email, send a message with subject or body 'help' to
> webkit-dev-request at lists.webkit.org
>
> You can reach the person managing the list at
> webkit-dev-owner at lists.webkit.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of webkit-dev digest..."
>
>
> Today's Topics:
>
> 1. Re: Question to the Adobe ApolloWebKit developers, tips and
> tricks to getting your "branch" to compile. (Fuenty, Chris)
> 2. Re: Re: [webkit-changes] [24723] trunk/WebCore (Maciej Stachowiak)
> 3. Re: Re: [webkit-changes] [24723] trunk/WebCore (Lars Knoll)
> 4. S60: Scriptable browser plugins (Volker Voecking)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 29 Jul 2007 08:45:25 -0500
> From: "Fuenty, Chris" <chris.fuenty at gmail.com>
> Subject: Re: [webkit-dev] Question to the Adobe ApolloWebKit
> developers, tips and tricks to getting your "branch" to
> compile.
> To: webkit-dev at lists.webkit.org
> Message-ID:
> <90de56650707290645i57f47874tb63c8aadb4428969 at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Last post, I have managed to get everything compiled. My question is
> though, how would I go about using this as a COM+ object, like I could
> with
> the old version of the early WebKit (before Safari3). I don't see any
> interface files within the webkit.apolloproj project. Is this strictly
> for
> use with apollo only? Or can it be used in other applications?
>
> Thx.
>
> -Z
>
> On 7/28/07, Fuenty, Chris <chris.fuenty at gmail.com> wrote:
> >
> > K. Here's all the externals i'm getting.
> >
> > Error 1 error LNK2001: unresolved external symbol _u_memcasecmp_3_4
> > WebPluginImpl.obj
> > Error 2 error LNK2001: unresolved external symbol _u_foldCase_3_4
> > WebPluginImpl.obj
> > Error 3 error LNK2001: unresolved external symbol _unorm_quickCheck_3_4
> > WebCore.lib
> > Error 4 error LNK2001: unresolved external symbol _unorm_normalize_3_4
> > WebCore.lib
> > Error 5 error LNK2001: unresolved external symbol _u_strToUpper_3_4
> > WebCore.lib
> > Error 6 error LNK2001: unresolved external symbol _u_strFoldCase_3_4
> > WebCore.lib
> > Error 7 error LNK2001: unresolved external symbol _u_charDirection_3_4
> > WebCore.lib
> > Error 8 error LNK2001: unresolved external symbol _u_islower_3_4
> > WebCore.lib
> > Error 9 error LNK2001: unresolved external symbol _u_totitle_3_4
> > WebCore.lib
> > Error 10 error LNK2001: unresolved external symbol _u_isdigit_3_4
> > WebCore.lib
> > Error 11 error LNK2001: unresolved external symbol _u_strToLower_3_4
> > WebCore.lib
> > Error 12 error LNK2001: unresolved external symbol
> > _u_getIntPropertyValue_3_4 WebCore.lib
> > Error 13 error LNK2001: unresolved external symbol _u_charType_3_4
> > WebCore.lib
> > Error 14 error LNK2001: unresolved external symbol _u_tolower_3_4
> > WebCore.lib
> > Error 15 error LNK2001: unresolved external symbol _uidna_IDNToASCII_3_4
> > WebCore.lib
> > Error 16 error LNK2001: unresolved external symbol _u_isUUppercase_3_4
> > WebCore.lib
> > Error 17 error LNK2001: unresolved external symbol _u_charMirror_3_4
> > WebCore.lib
> > Error 18 error LNK2001: unresolved external symbol _u_toupper_3_4
> > WebCore.lib
> > Error 19 error LNK2001: unresolved external symbol
> > _u_getCombiningClass_3_4 WebCore.lib
> > Error 20 error LNK2001: unresolved external symbol _ubrk_open_3_4
> > WebCore.lib
> > Error 21 error LNK2001: unresolved external symbol _ubrk_setText_3_4
> > WebCore.lib
> > Error 22 error LNK2001: unresolved external symbol _ubrk_following_3_4
> > WebCore.lib
> > Error 23 error LNK2001: unresolved external symbol _ubrk_isBoundary_3_4
> > WebCore.lib
> > Error 24 error LNK2001: unresolved external symbol _ubrk_next_3_4
> > WebCore.lib
> > Error 25 error LNK2001: unresolved external symbol _ubrk_preceding_3_4
> > WebCore.lib
> > Error 26 error LNK2001: unresolved external symbol _ubrk_first_3_4
> > WebCore.lib
> > Error 27 error LNK2001: unresolved external symbol _ubrk_current_3_4
> > WebCore.lib
> > Error 28 error LNK2001: unresolved external symbol _xmlStrndup
> WebCore.lib
> > Error 29 error LNK2001: unresolved external symbol __imp__xmlFree
> > WebCore.lib
> > Error 30 error LNK2001: unresolved external symbol
> > _xmlCreatePushParserCtxt WebCore.lib
> > Error 31 error LNK2001: unresolved external symbol _xmlSwitchEncoding
> > WebCore.lib
> > Error 32 error LNK2001: unresolved external symbol _xmlParseChunk
> > WebCore.lib
> > Error 33 error LNK2001: unresolved external symbol __imp__xmlMalloc
> > WebCore.lib
> > Error 34 error LNK2001: unresolved external symbol
> > _xmlRegisterInputCallbacks WebCore.lib
> > Error 35 error LNK2001: unresolved external symbol _xmlStrdup
> WebCore.lib
> > Error 36 error LNK2001: unresolved external symbol
> _xmlSAX2InternalSubset
> > WebCore.lib
> > Error 37 error LNK2001: unresolved external symbol _xmlFreeDoc
> WebCore.lib
> > Error 38 error LNK2001: unresolved external symbol _xmlInitParser
> > WebCore.lib
> > Error 39 error LNK2001: unresolved external symbol
> _xmlGetPredefinedEntity
> > WebCore.lib
> > Error 40 error LNK2001: unresolved external symbol
> > _xmlParseBalancedChunkMemory WebCore.lib
> > Error 41 error LNK2001: unresolved external symbol _xmlSAX2EntityDecl
> > WebCore.lib
> > Error 42 error LNK2001: unresolved external symbol _xmlStopParser
> > WebCore.lib
> > Error 43 error LNK2001: unresolved external symbol _xmlFreeParserCtxt
> > WebCore.lib
> > Error 44 error LNK2001: unresolved external symbol _xmlGetDocEntity
> > WebCore.lib
> > Error 45 error LNK2001: unresolved external symbol
> > _xmlRegisterOutputCallbacks WebCore.lib
> > Error 46 error LNK2001: unresolved external symbol _xmlSAX2StartDocument
> > WebCore.lib
> > Error 47 error LNK2001: unresolved external symbol _u_ispunct_3_4
> > WebCore.lib
> > Error 48 error LNK2001: unresolved external symbol "public: int
> __thiscall
> > WebCore::CSSParser::lex(void)" (?lex at CSSParser@WebCore@@QAEHXZ)
> > WebCore.lib
> > Error 49 error LNK2001: unresolved external symbol
> _ucnv_countAliases_3_4
> > WebCore.lib
> > Error 50 error LNK2001: unresolved external symbol
> > _ucnv_countAvailable_3_4 WebCore.lib
> > Error 51 error LNK2001: unresolved external symbol
> > _ucnv_cbFromUWriteUChars_3_4 WebCore.lib
> > Error 52 error LNK2001: unresolved external symbol _ucnv_toUnicode_3_4
> > WebCore.lib
> > Error 53 error LNK2001: unresolved external symbol
> > _ucnv_setFromUCallBack_3_4 WebCore.lib
> > Error 54 error LNK2001: unresolved external symbol _ucnv_getAlias_3_4
> > WebCore.lib
> > Error 55 error LNK2001: unresolved external symbol _ucnv_close_3_4
> > WebCore.lib
> > Error 56 error LNK2001: unresolved external symbol _ucnv_fromUnicode_3_4
> > WebCore.lib
> > Error 57 error LNK2001: unresolved external symbol
> > _UCNV_FROM_U_CALLBACK_ESCAPE_3_4 WebCore.lib
> > Error 58 error LNK2001: unresolved external symbol
> > _UCNV_FROM_U_CALLBACK_SUBSTITUTE_3_4 WebCore.lib
> > Error 59 error LNK2001: unresolved external symbol _ucnv_setFallback_3_4
> > WebCore.lib
> > Error 60 error LNK2001: unresolved external symbol
> _ucnv_setSubstChars_3_4
> > WebCore.lib
> > Error 61 error LNK2001: unresolved external symbol
> > _ucnv_getStandardName_3_4 WebCore.lib
> > Error 62 error LNK2001: unresolved external symbol
> > _ucnv_getAvailableName_3_4 WebCore.lib
> > Error 63 error LNK2001: unresolved external symbol _ucnv_open_3_4
> > WebCore.lib
> > Error 64 error LNK2001: unresolved external symbol _ucnv_getName_3_4
> > WebCore.lib
> > Error 65 error LNK2001: unresolved external symbol _u_isprint_3_4
> > WebCore.lib
> > Error 66 error LNK2001: unresolved external symbol _u_charDigitValue_3_4
> > WebCore.lib
> > Error 67 error LNK2001: unresolved external symbol
> > _ucnv_setToUCallBack_3_4 JavaScriptCore.lib
> > Error 68 error LNK2001: unresolved external symbol
> > _UCNV_TO_U_CALLBACK_STOP_3_4 JavaScriptCore.lib
> > Error 69 error LNK2001: unresolved external symbol _ucnv_toUChars_3_4
> > JavaScriptCore.lib
> >
> >
> >
> > On 7/28/07, Fuenty, Chris <chris.fuenty at gmail.com> wrote:
> > >
> > > 2 things. Sorry for getting it submitted as another thread, didn't
> > > realize you needed to include all past replies. 2nd, good job adding
> > > instructions to the wiki, as that should help out many people.
> > >
> > > --Z
> > >
> > > On 7/28/07, Fuenty, Chris <chris.fuenty at gmail.com > wrote:
> > > >
> > > > Allright, I'm out of town right now, but should be back in a few
> > > > hours. If I'm not sleeping by then, rather tired :(, I'm going to
> check
> > > > back on this list post.
> > > >
> > > > I've been working with the apollo projects in the M4 directory as
> > > > Chris' post has described. With JSCore, there was a bit of altering
> some
> > > > files and moving some stuff around, to get it to compile. Nothing
> major,
> > > > just a bit of troubleshooting, mainly in the hash values (.lut.h
> files) and
> > > > the bison-grammar generation. With a basic C++ knowledgebase I have
> I have
> > > > got it to compile without error.
> > > >
> > > > WebKit compiled right out of the box. No issues there
> > > >
> > > > Going on to compile WebKit, I have ran into a few issues, mainly
> with
> > > > the unresolved externals in WebCore and JavaScript Core libs. I'll
> post a
> > > > list of them when I get back, but from what I have looked at they
> seem to
> > > > have a similar function naming convention, and look like there
> coming from
> > > > another library, not WebCore/JSCore. Is there any other libraries
> (the
> > > > libxml, or any other of the libs pulled down from the inet from
> > > > ./install-win-extras) that I need to link upon?
> > > >
> > > > Also, regarding some changes I have found in WebKit, Does it support
> > > > plugins? I briefly looked through some files that seem to be
> directly
> > > > related, but haven't eximaned the sources of them to see whether or
> not they
> > > > are complete. While I'm at it, might as well ask.
> > > >
> > > > Keep me informed. Thanks
> > > >
> > > > --Z
> > > >
> > > >
> > >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.macosforge.org/pipermail/webkit-dev/attachments/20070729/2414a0f9/attachment-0001.html
>
> ------------------------------
>
> Message: 2
> Date: Sat, 28 Jul 2007 23:47:50 -0700
> From: Maciej Stachowiak <mjs at apple.com>
> Subject: Re: [webkit-dev] Re: [webkit-changes] [24723] trunk/WebCore
> To: Lars Knoll <lars at trolltech.com>
> Cc: Darin Adler <darin at apple.com>, WebKit Development
> <webkit-dev at lists.webkit.org>
> Message-ID: <99BB097E-DEA9-4198-9F46-B9247628AFF5 at apple.com>
> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
>
>
> On Jul 28, 2007, at 3:52 AM, Lars Knoll wrote:
>
> > On Saturday 28 July 2007 00:26:19 Maciej Stachowiak wrote:
> >> On Jul 27, 2007, at 11:36 AM, Lars Knoll wrote:
>
> >> Other organizations have requested the ability to use other XML
> >> parsers as well, such as expat. Seems like in the long run we want a
> >> different approach than just ifdefs in the XMLTokenizer.cpp file. It
> >> seems like the best would be some abstraction layer on top of the
> >> parser library, but if that is difficult then your option #2 sounds
> >> like a docent long-run approach. I would have expected just about
> >> every XML parsing library to have a SAX-like API, which shouldn't be
> >> too hard to abstract, but perhaps QXml works differently.
> >
> > I guess that assumption doesn't hold. QXmlStream is a streaming
> > parser with an
> > API that is very different from SAX. It IMO a whole lot simpler to
> > use than a
> > SAX like API and is inspired from similar APIs in the Java world. If
> > you're
> > interested, have a look at
> http://doc.trolltech.com/4.3/qxmlstreamreader.html
>
> I'm told libxml has a StreamReader-style API now as well, so if that's
> the better alternative, we could design the XML code around that style
> of API (though probably not right at the moment).
>
> Cheers,
> Maciej
>
>
>
> ------------------------------
>
> Message: 3
> Date: Sun, 29 Jul 2007 19:53:50 +0200
> From: Lars Knoll <lars at trolltech.com>
> Subject: Re: [webkit-dev] Re: [webkit-changes] [24723] trunk/WebCore
> To: Maciej Stachowiak <mjs at apple.com>
> Cc: Darin Adler <darin at apple.com>, WebKit Development
> <webkit-dev at lists.webkit.org>
> Message-ID: <200707291953.50559.lars at trolltech.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Sunday 29 July 2007 08:47:50 Maciej Stachowiak wrote:
> > On Jul 28, 2007, at 3:52 AM, Lars Knoll wrote:
> > > On Saturday 28 July 2007 00:26:19 Maciej Stachowiak wrote:
> > >> On Jul 27, 2007, at 11:36 AM, Lars Knoll wrote:
> > >>
> > >> Other organizations have requested the ability to use other XML
> > >> parsers as well, such as expat. Seems like in the long run we want a
> > >> different approach than just ifdefs in the XMLTokenizer.cpp file. It
> > >> seems like the best would be some abstraction layer on top of the
> > >> parser library, but if that is difficult then your option #2 sounds
> > >> like a docent long-run approach. I would have expected just about
> > >> every XML parsing library to have a SAX-like API, which shouldn't be
> > >> too hard to abstract, but perhaps QXml works differently.
> > >
> > > I guess that assumption doesn't hold. QXmlStream is a streaming
> > > parser with an
> > > API that is very different from SAX. It IMO a whole lot simpler to
> > > use than a
> > > SAX like API and is inspired from similar APIs in the Java world. If
> > > you're
> > > interested, have a look at
> > > http://doc.trolltech.com/4.3/qxmlstreamreader.html
> >
> > I'm told libxml has a StreamReader-style API now as well, so if that's
> > the better alternative, we could design the XML code around that style
> > of API (though probably not right at the moment).
>
> No, for the moment, I'd rather just go with the approach I've posted in
> bug
> 14791. Once there are requests for more parser backends, we could rethink
> this, but for now I think we have more urgent things to do.
>
> Cheers,
> Lars
>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 30 Jul 2007 13:52:00 +0200
> From: "Volker Voecking" <volker.voecking at gmail.com>
> Subject: [webkit-dev] S60: Scriptable browser plugins
> To: webkit-dev at lists.webkit.org
> Message-ID:
> <4b16b1880707300452x6974edd7se311e70fdd4c0778 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi,
>
> My environment is
> S60 Webkit trunk (r21772), S60_3rd SDK, Carbide.c++ 1.2 Express
>
> I compiled webkit/reindeer and it runs fine in the emulator.
> Looking a bit closer at the NPBitmap sample plugin and the source code
> of the S60 webkit port brings up the following question:
>
> Does the S60 WebKit port support scriptable browser plugins?
>
> If so, how does the Javascript binding work?
> Is it based on the Netscape Plugin API (NPClass; NPNHasMethod();
> NPNInvoke()... )?
>
> >From the NPBitmap sample plugin that is included in the S60_3rd SDK it
> seems that some S60 proprietary mechanism (Ecom-Plugin) is used for
> the interaction between browser and plugin.
> Is it possible e.g. to call a method or get/set a property of such an
> Ecom-Plugin from Javascript?
>
>
> Thanks,
> Volker
>
>
> ------------------------------
>
> _______________________________________________
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
> http://lists.webkit.org/mailman/listinfo/webkit-dev
>
>
> End of webkit-dev Digest, Vol 26, Issue 32
> ******************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.macosforge.org/pipermail/webkit-dev/attachments/20070730/ccb95eae/attachment.html
More information about the webkit-dev
mailing list