From: Alejandro Piñeiro Date: Mon, 18 Jul 2011 11:04:37 +0000 (+0200) Subject: Using atk_major_version on the binary_age X-Git-Tag: ATK_2_1_0~4 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=01cec7262f067b42f8359a3f4ccf3bca84f4b3e9;p=platform%2Fupstream%2Fatk.git Using atk_major_version on the binary_age This was required in order to avoid a shlib downgrade due the bump to 2.0 The ideal would be to update all the 1.0 stuff to 2.0. But that would required libraries using atk-1.0 to be modified in order to link against 2.0. Taking into account that ATK 2.0 is fully API and ABI compatible with ATK 1.0, this seems an overkill. --- diff --git a/configure.ac b/configure.ac index 6328c3b..0936fb8 100644 --- a/configure.ac +++ b/configure.ac @@ -21,17 +21,18 @@ m4_define([atk_micro_version], [1]) m4_define([atk_version], [atk_major_version.atk_minor_version.atk_micro_version]) -dnl The X.Y in -latk-X.Y line. This is expected to stay 1.0 until Atk 2. +dnl The X.Y in -latk-X.Y line. This is expected to stay 1.0 until Atk 3. m4_define([atk_api_version], [1.0]) dnl Number of releases since we've added interfaces m4_define([atk_interface_age], [1]) +dnl binary_age includes major version as ATK 2 is still fully API and ABI compatible m4_define([atk_binary_age], - [m4_eval(100 * atk_minor_version + 10 + atk_micro_version)]) + [m4_eval(10000 * atk_major_version + 100 * atk_minor_version + 10 + atk_micro_version)]) m4_define([lt_current], - [m4_eval(100 * atk_minor_version + 10 + atk_micro_version - atk_interface_age)]) + [m4_eval(10000 * atk_major_version + 100 * atk_minor_version + 10 + atk_micro_version - atk_interface_age)]) m4_define([lt_revision], [atk_interface_age]) m4_define([lt_age], [m4_eval(atk_binary_age - atk_interface_age)]) m4_define([lt_version_info], [lt_current:lt_revision:lt_age])