1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
|
# This is _NOT_ the library release version, it's an API version.
# Please read Chapter 6 "Library interface versions" of the libtool
# documentation before making any modification
#
# http://sources.redhat.com/autobook/autobook/autobook_91.html
#
# The version scheme used by Libtool tracks interfaces, where an interface
# is the set of exported entry points into the library. All Libtool libraries
# start with `-version-info' set to `0:0:0' -- this will be the default
# version number if you don't explicitly set it on the Libtool link command
# line. The meaning of these numbers (from left to right) is as follows:
#
# current
# The number of the current interface exported by the library. A current
# value of `0', means that you are calling the interface exported by this
# library interface 0.
#
# revision
# The implementation number of the most recent interface exported by this
# library. In this case, a revision value of `0' means that this is the
# first implementation of the interface.
#
# If the next release of this library exports the same interface, but has
# a different implementation (perhaps some bugs have been fixed), the
# revision number will be higher, but current number will be the same.
# In that case, when given a choice, the library with the highest revision
# will always be used by the runtime loader.
#
# age
# The number of previous additional interfaces supported by this library.
# If age were `2', then this library can be linked into executables which
# were built with a release of this library that exported the current
# interface number, current, or any of the previous two interfaces.
#
# By definition age must be less than or equal to current. At the outset,
# only the first ever interface is implemented, so age can only be `0'.
#
# 1. If you have changed any of the sources for this library, the revision
# number must be incremented.
# This is a new revision of the current interface.
#
# 2. If the interface has changed, then current must be incremented, and
# revision reset to `0'.
# This is the first revision of a new interface.
#
# 3. If the new interface is a superset of the previous interface (that is,
# if the previous interface has not been broken by the changes in this
# new release), then age must be incremented.
# This release is backwards compatible with the previous release.
#
# 4. If the new interface has removed elements with respect to the previous
# interface, then you have broken backward compatibility and age must be
# reset to `0'.
# This release has a new, but backwards incompatible interface.
#
# For example, if the next release of the library included some new commands
# for an existing socket protocol, you would use -version-info 1:0:1.
# This is the first revision of a new interface. This release is backwards
# compatible with the previous release.
#
# Later, you implement a faster way of handling part of the algorithm at the
# core of the library, and release it with -version-info 1:1:1. This is a new
# revision of the current interface.
#
# Unfortunately the speed of your new implementation can only be fully
# exploited by changing the API to access the structures at a lower level,
# which breaks compatibility with the previous interface, so you release it
# as -version-info 2:0:0. This release has a new, but backwards incompatible
# interface.
# curr:rev:age
LIBVERSION = 10:0:7
AM_CPPFLAGS = $(kinclude_CFLAGS) $(all_includes) -I$(top_srcdir)/include
AM_CFLAGS = -std=gnu99
if ENABLE_DEBUG
AM_CFLAGS += -g -g3 -ggdb -gdwarf-2 -DIPSET_DEBUG -Wall -Werror
else
AM_CFLAGS += -O2 -DNDEBUG
endif
SPARSE = sparse
SPARSE_FLAGS = -Wsparse-all -I../include $(SPARSE_EXT_FLAGS)
IPSET_AM_V_CHECK = $(ipset_am__v_CHECK_$(V))
ipset_am__v_CHECK_ = $(ipset_am__v_CHECK_$(AM_DEFAULT_VERBOSITY))
ipset_am__v_CHECK_0 = @echo " CHECK " $<;
|
