[webkit-dev] What libxml2 features are needed for WebKit?
eric at webkit.org
Tue Mar 25 15:10:04 PDT 2008
Again, I expect you can disable all of these safely.
You'd have to build your own copy of webkit however.
I intended to reply to the entire list, but must have hit the wrong button.
On Tue, Mar 25, 2008 at 2:45 PM, Leonid Romanov <Leonid.Romanov at sun.com> wrote:
> Thanks for your answer, Eric! I see that you replied directly to me, not
> to the mailing list. Did you hit wrong button?
> Anyway, if you don't mind I would like to ask you another question. You
> are right, WebKit doesn't directly calls any libxml2 functions related
> to the features I listed. However, I'm afraid that if I disable them I
> will end with subpar browser comparing to the Apple WebKit.
> Consider, for example, XInclude support. It is true that disabling it in
> libxml2 won't break WebKit build because of unresolved symbols. But what
> if WebKit doesn't really need to call any XInclude related functions
> from libxml2 in order to support it? May be it all happens
> transparently: libxml2 (with XInclude support enabled) internally
> resolves XInclude reference and asks WebKit to fetch external resource
> by calling some callback function with external resource URI as
> parameter, so no "WebKit<->XInclude" glue code on WebKit side is
> I said "what if" because I don't know how it all works in reality. I'm
> only guessing. Since libxml2 shipped with Mac OS has XInclude support
> enabled, one way to verify my guess is to see whether Apple WebKit
> supports XInclude or not : if it does then my guess is most likely
> right, if it doesn't then who knows. The problem is that I haven't found
> any docs on webkit.org which state what XML related specs are supported
> by Apple WebKit. But if my guess is right, then disabling XInclude in
> libxml2 is a bad thing to do if I want to have a browser as advanced as
> Apple WebKit. And I do want it. So, considering all what I said above,
> is it really OK to disable XInclude in libxml2?
> I used XInclude as example, but the same reasoning applies to DTD
> validation and XPointer.
> P.S. If this question is outside the scope of your knowledge just tell
> me so and I'll repost it to the mailing list as followup.
> On Tue, 2008-03-25 at 13:25 -0700, Eric Seidel wrote:
> > As far as I know, none of those features are required by WebKit. You
> > should be fine to link against a version of libXML2 which does not
> > include those.
> > -eric
> > On Tue, Mar 25, 2008 at 10:48 AM, Leonid Romanov <Leonid.Romanov at sun.com> wrote:
> > > Hi,
> > > I'm trying to minimize WebKit and dependents libraries footprint, so I'd
> > > like to know what libxml2 features that can be enabled/disabled via
> > > configure are needed for WebKit. To be more specific, does WebKit need:
> > > - HTML support
> > > - DTD validation
> > > - XInclude support
> > > - XPath support (does WebKit have its own XPath engine?)
> > > - XPointer support
> > >
> > > Could anyone shed some light on this, please?
> > >
> > > Thanks,
> > > Leonid.
> > >
> > >
> > >
> > > _______________________________________________
> > > webkit-dev mailing list
> > > webkit-dev at lists.webkit.org
> > > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
> > >
More information about the webkit-dev