[webkit-dev] Thoughts on building gdk version with internal cairo
mike.emmel at gmail.com
Thu Aug 17 08:34:34 PDT 2006
I think the best approach is to build the external cairo as a static
lib and link it in.
Or if the internal one is uptodate do it the same way. This would be
true for the jpeg and
png libs also.
I just built cairo static no problems. Except that the pc file does
not seem to work
for a static build I'll email the cairo list.
What we would need to do is change the build to build the internal
libs as static libraries
and drop them in some directory. If you want external you just make
that dir the target for
install for the static libs.
On 8/17/06, Mark Rowe <opendarwin.org at bdash.net.nz> wrote:
> Hi Krzysztof,
> I agree that it would be preferable to use the version of Cairo
> included with WebKit. It is a bit unreasonable to require testers to
> install a second version of Cairo alongside, or in place of their
> system version, on systems using Cairo 1.0.x (almost all distros
> AFAIK). When I last looked the version of Cairo in WebKit was itself
> too old to work with the GDK port, so a newer version would need to
> be merged in for this to work.
> Mark Rowe
The main reason I when external is I'm not happy with the cairo fon't api' s
And webkit can generally benifit from every single change made to
cairo to improve
the api's. Another problem I ran into for example in my SVG work is
there is no api
in cairo to see if the path is currently empty for a cairo context.
With that said I don't think it would be hard to change the bakefiles to make it
and option as long as the internal one was synced more often.
A better approach would be to build the external cairo as a .a file
and static link
I think this solves all the problems.
> On 17/08/2006, at 8:14 PM, Krzysztof Kowalczyk wrote:
> > Currently gdk project builds against cairo installed on the system.
> > What are people's thoughts on changing the default to build with cairo
> > sources included with webcore?
> > The disadvantage is that it generates a bigger binary than it would if
> > cairo shared library was used.
> > The advantage is that using exactly the same sources as other builds
> > would make chasing down bugs & incompatibilities easier (one source of
> > differences less).
> > But the main reason I would like to do that is that my cutting edge
> > Ubuntu 6.06 ships with cairo 1.0.4 that doesn't seem to have all
> > required functionality (e.g. cairo_scaled_font_text_extents) and I'm
> > rather scared upgrading a system-wide library (especially one on which
> > gnome/gtk depends on) to a newer, potentially incompatible version
> > (and I would rather not deal with having a second copy).
> > Any thoughts?
> > -- kjk
> > _______________________________________________
> > webkit-dev mailing list
> > webkit-dev at opendarwin.org
> > http://www.opendarwin.org/mailman/listinfo/webkit-dev
> webkit-dev mailing list
> webkit-dev at opendarwin.org
More information about the webkit-dev