From 0bb2901aa5d944e7e588a4fd9f57d3be96354dc5 Mon Sep 17 00:00:00 2001 From: Philip Withnall Date: Sun, 4 Oct 2015 13:35:38 +0100 Subject: build: Split GOA symbols out into a separate symbols file On some systems (Mac OS X) it is an error to include symbols in the symbols file which are not exported from the library. This can happen if building with --disable-goa (or --disable-gnome). Fix this by generating the symbols file dynamically. https://bugzilla.gnome.org/show_bug.cgi?id=754821 --- HACKING | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'HACKING') diff --git a/HACKING b/HACKING index 69177c23..32917c7b 100644 --- a/HACKING +++ b/HACKING @@ -95,7 +95,7 @@ Adding public API - All public API must have a gtk-doc comment, and be added to the docs/reference/gdata-sections.txt file, to include it in the documentation. The documentation comment must have a "Since" clause (see "Documentation comments" section). - - All public API must be listed in gdata/gdata.symbols. + - All public API must be listed in gdata/gdata-*.symbols. - Non-trivial API should have a test case added in the relevant test suite file in gdata/tests. Note that the "general" test suite file cannot make network requests in the course of running its test cases. @@ -157,7 +157,7 @@ deprecating API: If this isn't possible, the deprecated function should be split into a static function which contains all the code, and the public symbol should become a simple wrapper of this static function. This allows the static function to be used inside libgdata without causing deprecation warnings. - - Don't remove deprecated symbols from gdata.symbols. + - Don't remove deprecated symbols from gdata-*.symbols. - Don't forget to also deprecate related symbols, such as the getter/setter for a property (or vice-versa). -- cgit v1.2.1