[svn-r10627] Purpose:

Feature - libtool shared library versioning

Description:
Libtool provides a mechanism for different versions of the same shared
library to be distinguished.  Now this is applied to HDF5 when it is
built as a shared library.

Solution:
The version number is stored in config/lt_vers.am, and included in
src/Makefile.am.
This number will be automatically updated by bin/h5vers; developers
only need to update it when they change the API.

*** IMPORTANT ***
Any time the API changes, the version number in config/lt_vers.am must
be updated!



Platforms tested:
mir, eirene, verbena, modi4

Misc. update:

1 files changed, 26 insertions, 0 deletions

diff --git a/config/lt_vers.am b/config/lt_vers.am
new file mode 100644
index 0000000..a6a6cd6
--- /dev/null
+++ b/config/lt_vers.am
@@ -0,0 +1,26 @@
+# Add libtool shared library version numbers to the HDF5 library
+# See libtool versioning documentation online.
+LT_VERS_INTERFACE = 0
+LT_VERS_REVISION = 0
+LT_VERS_AGE = 0
+
+## If the API changes *at all*, increment LT_VERS_INTERFACE and
+## reset LT_VERS_REVISION to 0.
+##
+## If the API changes but no functions are removed, also increment
+## LT_VERS_AGE.
+## If any functions are removed from the API, reset LT_VERS_AGE
+## to 0.
+##
+## If the source changes but there are no API changes, increment
+## LT_VERS_REVISION.  This will happen automatically when
+## bin/h5vers is run, but doing it manually shouldn't hurt
+## anything.
+##
+## Note that this versioning system doesn't attempt to handle
+## the effects of the H5_V1_x_COMPAT flag.
+##
+## Since the revision number is automatically incremented by
+## bin/h5vers, don't move LT_VERS_REVISION from the fourth line
+## without also editing the script!
+