<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body>ABI: yes, application binary interface, so about compatibility with already compiled code linked to the MLT shared object library. <div><br></div><div>so: here most probably refers to shared object (library), the so file is the library file that can be used by multiple programs simultaneously without having to include or embed it into all these multiple programs. </div><div><br></div><div>Regards, </div><div>Harald </div><br><br>-------- Ursprüngliche Nachricht --------<br>Von: Roger Morton <ttguy1@gmail.com> <br>Datum: 07.02.2016 04:57 (GMT+01:00) <br>An: kdenlive <kdenlive@kde.org> <br>Betreff: [kdenlive] MLT version scheme to change <br><br>Dan Wrote:<br><br>"For the next release of MLT (soon) I was thinking of changing the version<br>scheme to reflect the so version number. IOW (In other words), it<br>would be like 6.0.0 (or possibly 7.0.0), and the major version will<br>change when the ABI changes."<br><br>Now I can't read this sentance very well. Urban dictionary helped a bit.<br><br>Is ABI = Application Binary Interface?<br><br>What does "so version number mean" ?<br><br>Anyway CMakeList.txt does this on melt versions<br><br># Minimum versions of main dependencies.<br>set(MLT_MIN_MAJOR_VERSION 0)<br>set(MLT_MIN_MINOR_VERSION 9)<br>set(MLT_MIN_PATCH_VERSION 8)<br><br>So I guess we don't have to worry because 6.0.0 is going to be greater<br>than 0.9.8<br>_______________________________________________<br>kdenlive mailing list<br>kdenlive@kde.org<br>https://mail.kde.org/mailman/listinfo/kdenlive<br></body></html>