~smcv/folks - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author	Files	Lines
2014-01-08	build: Don’t link backend libraries with libfolks-internal.la helper	Philip Withnall	1	-1/+0
	Because libfolks-internal.la is a libtool helper library, and is never actually installed, it gets statically linked into each backend. This means that the GObject types in it (such as FolksSmallSet) get duplicated between libfolks.so and each backend. This causes GObject errors when the backends are loaded and attempt to re-register types which already exist. This is a partial revert of commits: • 150858a0237291d8269d222defcb82f54c1125cf • ef76b7cacb5cfdf7963e5c2a2fe3bc8c1c97838e
2013-12-23	build: Only link the "endpoint" backend libraries against libfolks-internal	Travis Reitter	1	-2/+4
	This fixes a build-breaking bug introduced in commit 150858a023
2013-12-20	build: Ensure backends correctly link to internal folks libraries	Philip Withnall	1	-0/+1

2013-12-09	build: Allow backend libraries to have individual API versions	Philip Withnall	1	-2/+17
	The API version is included in the GIR file name, and only changes when API is broken or removed. If new backends, such as the dummy backend, are to have unstable APIs, having individual versions for each backend library is necessary to allow backend API breaks without breaking the whole of the folks API. The API version has not been added to the VAPI file name, though it should, because that would be a backwards-incompatible change. It can be added when folks next breaks API compatibility. https://bugzilla.gnome.org/show_bug.cgi?id=711544
2013-12-09	build: Factor common backends/*/lib makefilery into backend-library.mk	Philip Withnall	1	-0/+178
	This simplifies and standardises the build process for the installed backend libraries (libfolks-eds.so and friends). https://bugzilla.gnome.org/show_bug.cgi?id=711544