| Summary: | Make pycairo compile against gtk+ 2.7.x | ||
|---|---|---|---|
| Product: | cairo | Reporter: | Gustavo J. A. M. Carneiro <gjc> |
| Component: | general | Assignee: | Carl Worth <cworth> |
| Status: | RESOLVED FIXED | QA Contact: | cairo-bugs mailing list <cairo-bugs> |
| Severity: | normal | ||
| Priority: | high | ||
| Version: | 0.9.3 | ||
| Hardware: | x86 (IA32) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
make gdk_cairo_create conditionally defined depending on gtk+ 2.8 API availability
sorry, this is the correct patch |
||
|
Description
Gustavo J. A. M. Carneiro
2005-05-22 08:43:40 UTC
Created attachment 2741 [details] [review] make gdk_cairo_create conditionally defined depending on gtk+ 2.8 API availability Created attachment 2743 [details] [review] sorry, this is the correct patch PS: perhaps the only two cairo.gtk functions should move into pygtk (module gtk.gdk)? PyGTK has already branched for 2.8.. I should have given gdk_cairo_create a 'py' prefix to make it unique. Thanks for the patch, its now in cvs. It would be good for the two cairo.gtk functions to move into pygtk, then the module would only be needed for people with pygtk < 2.8 and could eventually be removed completely. Patch applied, closing bug report. I'm proposing making pygtk depend on pycairo. See http://bugzilla.gnome.org/show_bug.cgi?id=305844 Move bugs against "cvs" version to "0.9.3" so we can remove the "cvs" version. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.