[webkit-dev] Progressing on the Android port
darin at chromium.org
Mon May 16 10:52:59 PDT 2011
On Fri, May 13, 2011 at 1:48 PM, Lucas De Marchi <
lucas.demarchi at profusion.mobi> wrote:
> On Fri, May 13, 2011 at 5:35 PM, Holger Freyther <zecke at selfish.org>
> > On 05/12/2011 05:16 PM, Lucas De Marchi wrote:
> >> Hi Holger Freyther,
> >> I'm glad to hear you will use CMake as the build system. Take a look
> >> on the email I sent yesterday porting GTK to CMake, maybe it will help
> >> you. Since Android and Chromium/Linux have overlaps, do you think
> >> it'd be easy to build the Chromium port as well?
> > I am not sure about Chromium. When one tries to build Chromium a lot of
> > external code will be downloaded, I don't have the things in my tree
> right now
> > but IIRC these external modules are all having Gyp files so one would
> need to
> > convert these dependencies and it will be quite some work.
> Hummn... too bad. Looking at the gyp files, it doesn't seem difficult
> to convert them. But indeed it's quite some work.
Keep in mind that you'd also need to repeat this exercise whenever you
the latest version of those modules.
If you are planning to make use of more of the same code as Chromium, I
you will find that using GYP will be the path of least resistance.
> > I am having one specific issue with CMake right now, do you think it
> would be
> > possible to have defaults for WEBKIT_FEATURE(ENABLE_AS_IMAGE "Enable SVG
> > image" DEFAULT ON SVG)? E.g. I need to define ENABLE_GLIB as otherwise I
> > up having a '#define ENABLE_GLIB' in the cmakeconfig.h breaking the
> This is exactly the reason why I committed r86370 when doing the GTK
> port. Now you can do as I did for GTK:
> WEBKIT_FEATURE(ENABLE_GLIB_SUPPORT "Enable Glib support" ALWAYS ON)
> or ALWAYS OFF if you meant to unconditionally disable it.
> Lucas De Marchi
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev