[cairo] Win32 problems

[Owen Taylor]

On Wed, 2005-08-24 at 17:21 +0300, Nick Ameladiotis wrote:
> Oops, i've cc again to the list
> 
> One more question before giving up, when  CAIRO_INT_STATUS_UNSUPPORTED 
> is returned the previous call from
> _cairo_gstate_fill will also return the status to cairo_fill_preserve 
> which in result cause _cairo_set_error to be called.So it looks like 
> everything is normal as far as regarding compiling, since the fill_path 
> memeber in the backend is not specified

The code I have in _cairo_gstate_fill looks like:

    status = _cairo_surface_fill_path (gstate->operator,
                                       gstate->source,
                                       gstate->target,
                                       path,
                                       gstate->fill_rule,
                                       gstate->tolerance);

    if (status != CAIRO_INT_STATUS_UNSUPPORTED)
        return status;

    _cairo_traps_init (&traps);

   [...]

Otherwise, if the surface supports fill_path, do that, otherwise
fall through to a different operation.

> I realy cannot understand how come and mingw  works as expected, i've 
> tried both building with borlands c++ and msvc with same results.

Cairo works fine for other people compiling with MSVC

							Owen

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.freedesktop.org/archives/cairo/attachments/20050824/13d6cb50/attachment-0001.pgp