Minimum API level?

[Volker Krause]

On Tuesday, 15 January 2019 01:19:18 CET Aleix Pol wrote:
> On Mon, Jan 14, 2019 at 10:22 PM Volker Krause <vkrause at kde.org> wrote:
> > On Monday, 14 January 2019 21:08:56 CET Volker Krause wrote:
> > > Hi,
> > > 
> > > yet another version question: which is the minimum API level we want to
> > > support?
> > > 
> > > During the KF5Notification review going below 23 was suggested (still a
> > > relevant market share).
> > > 
> > > https://en.wikipedia.org/wiki/Android_version_history suggest anything
> > 
> > below
> > 
> > > 16 would be pointless (no market share anymore).
> > > 
> > > https://wiki.qt.io/Android specifies 13 as the lower limit that Qt
> > 
> > supports
> > 
> > > for applications.
> > > 
> > > https://developer.android.com/about/dashboards/ would suggest >= 19
> > 
> > based on
> > 
> > > market share.
> > > 
> > > I'm asking as I just tried to test KF5Notifications on API level 21 (via
> > 
> > KDE
> > 
> > > Itinerary), which failed:
> > 
> > > - Aleix's APK:
> > dlopen("/data/data/org.kde.itinerary/lib/libQt5Network.so",
> > 
> > > RTLD_LAZY) failed: dlopen failed: cannot locate symbol
> > > "ASN1_STRING_get0_data" referenced by "libQt5Network.so"...
> > > - my local build: dlopen("/data/data/org.kde.itinerary/lib/
> > > libKF5CoreAddons.so", RTLD_LAZY) failed: dlopen failed: cannot locate
> > 
> > symbol
> > 
> > > "__register_atfork" referenced by "libKF5CoreAddons.so"...
> > 
> > FTR, that was a local issue, I got API level 21 working with my build,
> > without
> > requiring code changes even, so it's not as bad as I had initially feared.
> > 
> > That makes [19, 21] the interesting range to decide from I think.
> > 
> > > Both APKs work fine on API level 24.
> > > 
> > > What do you think?
> > > 
> > > Regards,
> > > Volker
> 
> Does this mean we need to fix something on the binary-factory builds?

Possible, I don't know what though. I'm using the same versions locally, the 
only difference seems to be the self-compiled Qt with linked OpenSSL compared 
to me using the Qt SDK binaries. I don't see how that would result in 
Qt5Network referencing that symbol though, from looking at the Qt code, nor 
why that is even API level dependent...

The last successful build from binary factory (still using the old setup) 
doesn't seem to have this problem, but hard to tell for sure as that also 
crashes on startup (due to a meanwhile fixed issue in KNotifications).

Regards,
Volker
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-android/attachments/20190115/fdf508e3/attachment.sig>