On Monday 28 April 2014 05:37:40 Dimitar Dobrev wrote: <snip> > My problem (and, I'd say, any binding developer's) is > that I can't tell users "my binding is great, you just need to compile Qt > yourselves because the binary downloads don't work well enough" - nobody's > going to use it.
But whoever is going to use your bindings will also have to download some binary for the bindings, right? So why don't you add the missing functions in a wrapper there and compile it alongside your bindings? I.e. what Simon said: > But the ABI promise of Qt remains, so can't you create a library yourself > that basically contains the inline functions you need and otherwise > references the exported symbols from Qt? Your bindings will need to ship > that library, but it should continue to work with newer versions of Qt. (It > just needs an update when the inline functions change in a newer Qt > version) Why does this not work for you? Note that you could even make such a wrapper library official and share it with other bindings. Maybe it could even become an official Qt module! Then eventually consumers of bindings people would just need to download the additional binding-wrapper libraries and everything works as it should? Bye -- Qt Developer Days 2014 - October 6 - 8 at BCC, Berlin Milian Wolff | milian.wo...@kdab.com | Software Engineer KDAB (Deutschland) GmbH&Co KG, a KDAB Group company Tel. Germany +49-30-521325470, Sweden (HQ) +46-563-540090 KDAB - Qt Experts - Platform-independent software solutions _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development