[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #21200] Cairo version dependency and other nuisances

From: Mark Tracy
Subject: [bug #21200] Cairo version dependency and other nuisances
Date: Sun, 30 Sep 2007 21:14:57 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20061023 SUSE/ Firefox/


                 Summary: Cairo version dependency and other nuisances
                 Project: GNUstep
            Submitted by: tracy454
            Submitted on: Sunday 09/30/2007 at 21:14
                Category: None
                Severity: 3 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any



Sometime in the last month or so, back-0.13 (Trunk) started using API calls
from Cairo-1.4 for the Cairo backend. This was not noted in the ChangeLog, nor
is it checked in configure. I noticed it because Suse 10.2 provides

Installing Cairo-1.4.2 at least allowed me to build and run the Cairo
backend. (Doesn't work, but that is another story.) 

However, when I tried Cairo-1.4.10, the current stable release, CairoGState.m
copyWithZone: generated errors "Cairo status out of memory in copy path." A
quick peek with valgrind didn't reveal any memory errors there.

A final nuisance is font names. Since the cairo backend uses FreeType, the
selection of fonts is at the mercy of the distribution. In my case, Suse 10.2
provides dozens of fonts, none of which is named "Helvetica." There is "Adobe
Helvetica." I'm not sure what to suggest, but perhaps this is best handled in
the documentation. My solution was to set the appropriate defaults for NSFont
and NSBoldFont.

I'm not sure what the intent is with respect to Cairo version requirements,
but I thought it worth pointing out.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]