summaryrefslogtreecommitdiffstats
path: root/src/virt-glib-compat.h
Commit message (Collapse)AuthorAgeFilesLines
* Drop old compatibility codeEduardo Lima (Etrunko)2016-02-181-83/+0
| | | | | | With glib requirements now being 2.38, these functions do not make sense anymore. Signed-off-by: Eduardo Lima (Etrunko) <etrunko@redhat.com>
* glib-compat: Use g_new0(GMutex, 1) if GLib >= 2.31Fabiano Fidêncio2015-07-221-0/+4
| | | | | | | | | | Since 2.31, g_mutex_new() is deprecated. Based on commit 2dc7476d32a9e158e688486e8f184c719c53bb4c from libvirt-glib. Original author: Daniel P. Berrange <berrange@redhat.com> Related to: rhbz#1243228
* glib-compat: group definitions and functionsFabiano Fidêncio2015-07-221-2/+0
| | | | | There is no need to have more than one glib version checking for the same version, in the same file. Let's just group them all.
* Add G_SOURCE_REMOVE to vir-glib-compatFabiano Fidêncio2015-03-111-0/+5
| | | | | G_SOURCE_REMOVE was introduced in GLib 2.32 and has its value defined as FALSE.
* Fix compilation with older glib versionsChristophe Fergeau2013-03-201-0/+20
| | | | | | Recent commits introduced use of g_clear_object and g_byte_array_new_take which are only present respectively in glib 2.28 and 2.32
* Bump glib > 2.22, add compat fileMarc-André Lureau2012-07-231-0/+56
We use API from 2.22, and some from further version. Add virt-glib-compat.h fallback file for those.