-
Committer:
Carlos R. Mafra
-
Author(s):
Christophe CURIS
-
Date:
2023-08-12 20:53:52 UTC
-
Revision ID:
git-v1:2264ed9de667b7f02ee8dab35a12ce5e80af427f
Fix calculation of version number in the library mapfiles
As reported by Andreas Metzler, the latest API change in lib WRaster caused
a compatibility issue because the internal version number was increased.
To correctly handle this situation, this patch does 2 things:
- do not discard the 2 last number in the "c:r:a" version, because we need them;
- when calculating the version for the mapfile, use the formula that is
suggested in libtool's documentation.
The purpose of the formula is that when API is changed, if a new function
is added then the version is not incremented to reflect that we are still
compatible with current binaries, it will be incremented only when there
is a break in compatibility.