[cairo] cairomm 1.6.0 fails with cairo 1.6.4 + quartz on Mac OS X

Vladimir Vukicevic vladimir at pobox.com
Fri Apr 25 09:23:49 PDT 2008

On Apr 25, 2008, at 8:37 AM, Jonathon Jongsma wrote:
> Yes, we do essentially the same thing in cairomm (we have separate
> xlib_surface.h and quartz_surface.h headers).  The problem in this
> case is that we currently have some code in
> Cairo::Context::get_target() that checks which kind of surface it is
> and creates the appropriate wrapper type for that surface (e.g. an
> XlibSurface, a QuartzSurface, ImageSurface, etc.).  So that's
> obviously pulling in all of the platform surface types.  (Note that
> this is in the source file, not a header, so it's not a problem for
> users, only for building cairomm itself).  But it appears that we may
> need to find a smarter way to do this...

The easiest thing to do here would be to manually typedef/declare the  
minimum necessary types for each platform -- this is usually only one  
or two types.  That way you can avoid including the entire system  

     - Vlad

More information about the cairo mailing list