<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div class="">Bas,</div><div class=""><br class=""></div><div class="">Here’s an annotated version of me following the steps in your link:</div><div class=""><br class=""></div><br class=""><div class="">1. Start with version information of ‘0:0:0’ for each libtool library.<br class=""></div><div class=""><br class=""></div><div class=""> Well, we start with 20.0.1</div><div class=""><br class=""></div><div class="">2. Update the version information only immediately before a public release of your software. More frequent updates are unnecessary, and only guarantee that the current interface number gets larger faster.<br class=""></div><div class=""><br class=""></div><div class=""> Did this.</div><div class=""><br class=""></div><div class="">3. If the library source code has changed at all since the last update, then increment revision (‘c:r:a’ becomes ‘c:r+1:a’).<br class=""></div><div class=""><br class=""></div><div class=""> The code has changed since the last update, so now we’re at 20.1.1</div><div class=""><br class=""></div><div class="">4. If any interfaces have been added, removed, or changed since the last update, increment current, and set revision to 0.<br class=""></div><div class=""><br class=""></div><div class=""> We’ve added new interfaces since the last version, so 21.0.1</div><div class=""><br class=""></div><div class="">5. If any interfaces have been added since the last public release, then increment age.<br class=""></div><div class=""><br class=""></div><div class=""> As stated above, new interfaces were added, so 21.0.2</div><div class=""><br class=""></div><div class="">6. If any interfaces have been removed or changed since the last public release, then set age to 0.<br class=""></div><div class=""><br class=""></div><div class=""> No removed or changed interfaces this time around.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">I know I’ve mucked these numbers up several times before but this time around I am not convinced</div><div class="">it is the case. I am of course happy to be proven otherwise!</div><div class=""><br class=""></div><div class="">/Kristian</div><br class=""><br class=""><blockquote type="cite" class="">On 26 Oct 2020, at 13:48, Sebastiaan Couwenberg <<a href="mailto:sebastic@xs4all.nl" class="">sebastic@xs4all.nl</a>> wrote:<br class=""><br class="">On 10/26/20 1:34 PM, Kristian Evers wrote:<br class=""><blockquote type="cite" class="">That’s weird, I’ve set them exactly the same in both CMake and autotools:<br class=""><a href="https://github.com/OSGeo/PROJ/commit/3bd548d816f141b617c7b3252e22b4f0b7fdd352" class="">https://github.com/OSGeo/PROJ/commit/3bd548d816f141b617c7b3252e22b4f0b7fdd352</a> <https://github.com/OSGeo/PROJ/commit/3bd548d816f141b617c7b3252e22b4f0b7fdd352><br class=""><br class="">Is this perhaps because PROJ_API_VERSION in CmakeLists.txt should be set to<br class="">current-age instead of just current?<br class=""></blockquote><br class="">PROJ_API_VERSION is used to set the SOVERSION for CMake, so this must<br class="">match the calculated SOVERSION (current - age) for Autotools.<br class=""><br class="">Since the intention is to bump the ABI, version-info should be 21:0:0.<br class=""><br class="">See the libtool manual for more information:<br class=""><br class=""><a href="https://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html" class="">https://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html</a><br class=""><br class="">Kind Regards,<br class=""><br class="">Bas<br class=""><br class="">-- <br class="">GPG Key ID: 4096R/6750F10AE88D4AF1<br class="">Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1<br class="">_______________________________________________<br class="">PROJ mailing list<br class="">PROJ@lists.osgeo.org<br class="">https://lists.osgeo.org/mailman/listinfo/proj<br class=""></blockquote><br class=""></body></html>