Package Details: android-qt5-armeabi-v7a 5.11.2-3

Git Clone URL: (read-only)
Package Base: android-qt5-armeabi-v7a
Description: Qt 5 for Android
Upstream URL:
Licenses: GPL3, LGPL
Groups: android-qt5
Submitter: hipersayan_x
Maintainer: hipersayan_x
Last Packager: hipersayan_x
Votes: 17
Popularity: 0.562287
First Submitted: 2016-02-29 14:37
Last Updated: 2018-11-19 20:44

Dependencies (17)

Required by (0)

Sources (3)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

Martchus commented on 2018-11-20 15:24

What do you think?

I like it. It makes sense to put the whole target platform at the beginning. So go ahead and change the package name. I'll adapt my packages as soon as I have time (likely I wait for Qt 5.12.0).

BTW: To rename an AUR package, you have to upload it as a new package. To transfer comments and votes, you can then create a merge request.

hipersayan_x commented on 2018-11-20 14:05

Yep, we need a common file structure before we have hundreds of Android packages populating the AUR.
My other idea is to change the package names to follow more closely the name of the Android images, for example in the AUR you have:


So the android packages could have the form: android-architecture-name. And the architectures could be:

aarch64 (this one based in the toolchain)

So for users it will be much easier to correlate the package names with the system, also it will be easier to find all packages available for the same architecture. What do you think?

Martchus commented on 2018-11-19 22:07

Nice, you're adapting the structure of my Android package for OpenSSL, iconv, Kirigami and Boost. By the way, I'm going to upload these to the AUR soon. So far the aarch64 variants can be found in my PKGBUILDs repo. (I'm just pointing that out to prevent you from duplicating this effort.)

hipersayan_x commented on 2018-11-19 21:14

From now on, android-qt5-* will have the following file structure:


The purpose of this change is to coexist with other 3rd-party Android libraries, and create an homogeneous development environment. More changes would come in the future in order to improving the situation.

Apologies for the inconvenience caused.

Martchus commented on 2018-10-30 14:07

I prefer using the latest SDK/NDK as well. And I wouldn't bet that the recommendations are still up-to-date.

Only for Java it seems one really has to stick to an old version. (Java 8 was the latest version I could run androiddeployqt with.)

hipersayan_x commented on 2018-10-30 12:26

I prefer to keep these packages working with latest NDK version only, but someone else can create a package for working with older versions.

Kicer commented on 2018-10-27 21:37

@hipersayan_x and @kuzulis: I'm getting the same error. Both Qt, and Arch sites ( suggest using NDK10e

hipersayan_x commented on 2018-10-20 20:10

Only latest NDK version is supported, older versions does not receives support from Google and are not recommended for new devices AFAIK.

kuzulis commented on 2018-10-20 15:07

It does not compiles with NDK10e, returns:

Info: creating super cache file /home/denis/Downloads/android-qt5-armeabi-v7a/src/qt-everywhere-src-5.11.2/.qmake.super Project ERROR: Cannot run target compiler '/opt/android-ndk/toolchains/llvm/prebuilt/linux-x86_64/bin/clang++'. Output: =================== sh: /opt/android-ndk/toolchains/llvm/prebuilt/linux-x86_64/bin/clang++: No such file or directory

But when I created a symlink:

sudo ln -s /opt/android-ndk/toolchains/llvm-3.6 /opt/android-ndk/toolchains/llvm

then the Qt5 config fails with:

ERROR: Qt requires a compliant STL library.

ERROR: C++11 <random> is required and is missing or failed to compile.

ERROR: detected a std::atomic implementation that fails for function pointers. Please apply the patch corresponding to your Standard Library vendor, found in qtbase/config.tests/atomicfptr

UPD: A workaround is to replace -xplatform android-clang with -xplatform android-g++

Shatur commented on 2018-10-04 11:43

@hipersayan_x thank you! It works!