On sexta-feira, 26 de julho de 2013 12:10:59, BogDan wrote: > >> In this case I'll keep my -1 for that patch > >> > >> Can't cmake scripts be changed to work with SONAME set to > >> libQt5XXXXX.so ? > > > > Why don't we do on Android what we do everywhere else? > > > > soname: libQt5XXXX.so.5 > > actual file: libQt5XXXX.so.5 > > > > No need to ship the symlink in .apk. It's only necessary in the SDK / > > sysroot. > > Because a few things will still stop to work (e.g. qtc android plugin) :) .
A Qt Creator plugin is not an argument, since we can fix the plugin :-) > Also AFAIK everywhere else libQt5XXXX.so.5 is a symlink > to libQt5XXXX.so.5.major which is a symlink to libQt5XXXX.so.5.major.minor > . If you don't plan to ship libQt5XXXX.so.5.major.minor and we don't use > symlinks, then personally I don't see any reason to add an extra .5 to the > end of the file name as long as the file name already contains a 5 ... Right. libQt5XXXX.so.5 -> libQt5XXXX.so.5.x.y. Is there a restriction in shipping the symlinks in .apk? Anyway, the advantage is that we don't have to fix qmake and cmake and everything else that assume that there is a soname, and computes that soname. Instead of making Android different and then adding more conditionals, we should make Android more similar. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
