SUBDIRS=. Tests
+AM_CFLAGS=-g
MAINTAINERCLEANFILES=Makefile.in
INCLUDES= -I$(top_srcdir)/src/include \
@CFLAGS_SimGrid@
Virtu/virtu_sg.h \
DataDesc/ddt_parse.yy.l DataDesc/ddt_parse.yy.c
-VERSION_INFO=-version-info 0:1:0
+VERSION_INFO= -release 20040722 -version-info 0:0:0
+# from `info libtool "Updating version info"`
+# and `info libtool "Release numbers"`
+#
+# A) For stable library (interface wise), you should use --version-info:
+#
+# - Begin with C:R:A = 0:0:0 (ie here, VERSION_INFO= -version-info 0:0:0)
+# - Do not update it before public release (keep numbers small)
+#
+# ----------------------------------------------------------------------+
+# + Interface | code of existing | Interface | New version info |
+# | removal/change? | interface changed? | addition? | |
+# +-----------------+--------------------+-----------+------------------+
+# | yes | must be yes ;) | | C++ : 0 : 0 |
+# | no | yes | yes | C : R++ : A++ |
+# | no | yes | no | C : R++ : A |
+# | no | no | yes | C : R : A++ |
+# | no | no | no | C : R : A |
+# +-----------------+--------------------+-----------+------------------+
+#
+# B) For rapidely changing library, you should go for the -release flag
+#
+# It modifies the library name, and you thus cannot say that a library
+# using this trick is ready for a "stable" release (say, in Debian).
if HAVE_SG
lib_LTLIBRARIES= libgrasrl.la libgrassg.la
