| commit | 2264ed9de667b7f02ee8dab35a12ce5e80af427f | |
| author | Christophe CURIS <christophe.curis@free.fr> | |
| Sat, 12 Aug 2023 20:35:52 +0000 (12 22:35 +0200) | ||
| committer | Carlos R. Mafra <crmafra@gmail.com> | |
| Sat, 12 Aug 2023 20:53:52 +0000 (12 21:53 +0100) | ||
| tree | a5512476194d945c3c9d7f30a8b1c550c32a1a55 | treesnapshot (tar.gz zip) |
| parent | d0aa2cefcdd3ea72fa463213314757647cde46b3 | commitdiff |
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.
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.
| script/generate-mapfile-from-header.sh | diffblobblamehistory |