Package Details: android-aarch64-qt5 5.15.0-1

Git Clone URL: (read-only, click to copy)
Package Base: android-aarch64-qt5
Description: Qt 5 for Android
Upstream URL:
Licenses: GPL3, LGPL
Groups: android-qt5
Submitter: hipersayan_x
Maintainer: hipersayan_x
Last Packager: hipersayan_x
Votes: 13
Popularity: 0.62
First Submitted: 2018-11-22 19:14
Last Updated: 2020-06-03 18:52

Dependencies (26)

Required by (1)

Sources (3)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

Martchus commented on 2019-10-04 20:27

@Emeric I believe the mechanism behind this "Skipping .... It has unmet dependencies ..." message is actually for excluding plugins when the corresponding Qt module isn't used anyways. That's presumably androiddeployqt's way to decide which plugins to bundle and which not. Maybe the recent change to use system libjpeg (rather than the version bundled with Qt) causes this issue. It is likely that upstream never tested using system libjpeg under Android (they not even allowed to find the library via pkg-config, see my patch:

You can possibly "trick" androiddeployqt by linking your app against libjpeg. Maybe it also works to add libjpeg explicitly to "android-extra-libs" (within the JSON file for androiddeployqt). Maybe it also works to add the plugin explicitly to "android-extra-plugins". Just play around with it...

But this sounds like an upstream bug (although it has likely very low prio for them). To file a bug it would be good to share your project or to come up with a minimal project to reproduce.

Emeric commented on 2019-10-04 14:34

The jpeg plugin is not shipped in my apk with the 5.13 release, I'm not sure why but I do have this in my traces: -- Skipping /opt/android-libs/aarch64/plugins/imageformats/ It has unmet dependencies: lib/ I can see the file aarch64/lib/ Other image plugins are working. Also, could we maybe create a forum post (or anything) for all issues related to android and arch developement and packaging?

hipersayan_x commented on 2019-09-27 02:20

Well I hope they at least give the option to configure those paths instead of forcing us to do some some hackery to make the thing work :/

Martchus commented on 2019-09-26 15:10

I hope this change will not interfere with our way of packaging Qt for Android. And I'm currently using androiddeployqt via CMake which hopefully continues to work like before as well. The change to the directory structure mentioned in the ticket description (libs folder will have an ABI subfolder libs/armeabi-v7a, libs/arm64-v8a,etc) sounds scary. I hope they didn't implement it that way in the end...

Martchus commented on 2019-09-11 08:24

@hipersayan_x Ok, I'll try to fix the architectures when I have time. I can also try to user your environment packages. (The I'm using is taken from the OpenSSL documentation.) Maybe that also just fixes the problem.

hipersayan_x commented on 2019-09-10 23:48

@Martchus I have updated the package with your changes but since the openssl x86 packages does not compiles I did not added it as a dependency, if possible I want all architectures to have equal support.

hipersayan_x commented on 2019-09-09 23:26

@Martchus ok no problem, I will check it.

Martchus commented on 2019-09-09 20:53

@hipersayan_x I added the packages to the AUR but haven't tested them yet.

hipersayan_x commented on 2019-09-09 15:44

@Martchus Will check thanks. Also, can you upload the x86 and x86-64 packages for openssl?

Martchus commented on 2019-09-07 18:25

Update my OpenSSL-enabled version to 5.13.1:

I configured it now to use system zlib, libpng and libjpeg. This works nicely with your packages for these libraries. I also tested making and running an APK with CMake/androiddeployqt.

For libjpeg a patch is required to enable pkg-config detection (see link above). I guess it can be upsteamed:

Maybe it makes also sense to upstream the other patches?