Mercurial > pidgin.yaz
view pidgin/plugins/musicmessaging/Makefile.am @ 32138:e2c6e4fc3c84
Start looking at the GError parameter every time we call these functions:
- gdk_pixbuf_loader_write
- gdk_pixbuf_loader_close
- gdk_pixbuf_new_from_file
- gdk_pixbuf_new_from_file_at_size
- gdk_pixbuf_new_from_file_at_scale
There are times when gdkpixbuf returns a semi-invalid GdkPixbuf object and
also sets the GError. If this happens we want to discard and ignore the
GdkPixbuf object because it can cause problems. For example, calling
gdk_pixbuf_scale_simple() causes gdkpixbuf to rapidly consume memory in
an infinite loop. And that's bad.
This commit adds some helper functions to gtkutils.[c|h] that make it a
little easier to check the GError value. We should use them everywhere
we call any of the above functions.
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Wed, 22 Jun 2011 07:07:28 +0000 |
parents | e33a91b8b8f6 |
children |
line wrap: on
line source
EXTRA_DIST = \ music.png musicmessagingdir = $(libdir)/pidgin musicmessaging_la_LDFLAGS = -module -avoid-version if PLUGINS if ENABLE_DBUS musicmessagingpixdir = $(datadir)/pixmaps/pidgin/buttons musicmessagingpix_DATA = music.png musicmessaging_LTLIBRARIES = musicmessaging.la musicmessaging_la_SOURCES = \ musicmessaging.c musicmessaging_la_LIBADD = $(GTK_LIBS) $(DBUS_LIBS) CLEANFILES = music-messaging-bindings.c .PHONY: always $(top_builddir)/libpurple/dbus-types.h: always cd $(@D) && $(MAKE) $(AM_MAKEFLAGS) $(@F) music-messaging-bindings.c: $(top_srcdir)/libpurple/dbus-analyze-functions.py $(musicmessaging_la_SOURCES) cat $(srcdir)/$(musicmessaging_la_SOURCES) | \ $(PYTHON) $(top_srcdir)/libpurple/dbus-analyze-functions.py --export-only > $@ $(musicmessaging_la_OBJECTS) musicmessaging.so: music-messaging-bindings.c $(top_builddir)/libpurple/dbus-types.h endif endif AM_CPPFLAGS = \ -DDATADIR=\"$(datadir)\" \ -I$(top_builddir)/libpurple \ -I$(top_srcdir)/libpurple \ -I$(top_srcdir)/pidgin \ $(DEBUG_CFLAGS) \ $(GTK_CFLAGS) \ $(DBUS_CFLAGS)