Arch Linux User Repository

I'll drop this package, I been thinking and there are a lot of strong reasons not to waste any time maintaining it.
KDE doesn't provide an easy way to download the entire Qt source code in a single package, like in the official Qt releases.
Also, KDE doesn't provides tagged versions, I've to keep tracking manually the latest commits, or converting it to a git package.
It will require to split this package into 47x4 packages, 47 Qt modules and 4 architectures to maintain, that's 188 packages to maintain, absurd!
Cloning a git repository is slower than just downloading a source package file, making the build even much slower and painful.
Is a lot of work for something that will be dead in 1 year or 2 at most.
Good luck to the one that will step up to take care of this monstrosity, to the rest of developers, don't be lazy and consider switching to Qt6.

Let's see how this will work out: https://www.qt.io/blog/aab-support-in-qt-for-android

For us it likely still makes most sense to keep the architectures distinct. This feature makes not much sense if only Qt's build system supports it but not the other of libraries one might need to deploy. Besides, adding further complexity to the build system sounds like shooting yourself in the foot to me. Maybe the same could be achieved using distinct builds for the architectures as well. But Qt is transitioning to CMake anyway which only supports targeting one platform at a time (as far as I know). So they will likely need to drop their hacks again anyways.

Package fixed.

@genelocated the bug has been reported here. Will see if I can do something in my side or if we must wait until a new Qt release.

==> Making package: android-armv7a-eabi-qt5 5.12.3-1 (Mon 10 Jun 2019 09:54:23 PM CST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting build()...
+ cd qtbase
+ /home/genel/.cache/yay/android-armv7a-eabi-qt5/src/qt-everywhere-src-5.12.3/qtbase/configure -
top-level -confirm-license -opensource -silent -prefix /opt/android-libs/armv7a-eabi -examplesdi
r /opt/android-libs/armv7a-eabi/share/qt5/examples -testsdir /opt/android-libs/armv7a-eabi/share
/qt5/tests -xplatform android-clang -nomake tests -nomake examples -android-sdk /opt/android-sdk
 -android-ndk /opt/android-ndk -android-ndk-host linux-x86_64 -android-toolchain-version 4.9 -sk
ip qttranslations -skip qtserialport -no-warnings-are-errors -pkg-config -qt-zlib -qt-freetype -
android-arch armeabi-v7a -android-ndk-platform android-22 -release
Creating qmake...
Done.
Info: creating super cache file /home/genel/.cache/yay/android-armv7a-eabi-qt5/src/qt-everywhere
-src-5.12.3/.qmake.super
Info: creating cache file /home/genel/.cache/yay/android-armv7a-eabi-qt5/src/qt-everywhere-src-5
.12.3/.qmake.cache
Info: creating stash file /home/genel/.cache/yay/android-armv7a-eabi-qt5/src/qt-everywhere-src-5
.12.3/.qmake.stash

This is the Qt Open Source Edition.

You have already accepted the terms of the Open Source license.

Running configuration tests...
Checking for gold linker... no
Checking for valid makespec... Note: Also available for Linux: linux-clang linux-icc

ERROR: Cannot compile a minimal program. The toolchain or QMakeSpec is broken.

Check config.log for details.
==> ERROR: A failure occurred in build().
    Aborting...
Error making: android-armv7a-eabi-qt5

@tomicooler That patch was also used by the AUR package to fix https://bugreports.qt.io/browse/QTBUG-73141. But the package layout has been switched back since then so I suppose I should drop the patch, too.

@Martchus thanks a lot! :)

I think it will work. OpenSSL was found during the configure phrase. I noticed that this patch is not needed on my environment: 0002-Fix-androiddeployqt-search-paths.patch. The original path looks good.

@tomicooler Have a look at my Android packages for Qt 5 and OpenSSL: https://github.com/Martchus/PKGBUILDs

The Qt 5 packages are actually based on this one (although they are now slightly different). I actually tested (for aarch64) and at least a simple HTTPS test with Qt Network worked.

Hi all,

I would like to create a Qt application that needs openssl. (https is needed for Qt Location - Maps "osm" plugin).

How to add openssl for this Qt build? I have tried multiple things: First, I installed multilib/lib32-openssl and multilib/lib32-openssl-1.0 before compiling this Qt. Even though openssl was installed, I saw that the Qt's configure did not find it. So my Qt has no SSL support.

Anyway I tried to build and ship custom openssl for my application. Using the android-ndk toolchains (clang), I used the akontsevich's github project for build. This did not help, because my Qt was built without SSL.

Can anybody help me on this? Thank you for your time!

https://doc.qt.io/qt-5/android-openssl-support.html https://github.com/akontsevich/openssl-android-build

compiling src/pcre2_match_data.c                                                                                                                                                                                    
make[4]: Entering directory '/tmp/yaourt-tmp-patrick/aur-android-armv7a-eabi-qt5/src/qt-everywhere-src-5.12.1/qtbase/src/android/jar'                                                                               
javac -source 6 -target 6 -Xlint:unchecked -bootclasspath /opt/android-sdk/platforms/android-22/android.jar -cp /tmp/yaourt-tmp-patrick/aur-android-armv7a-eabi-qt5/src/qt-everywhere-src-5.12.1/qtbase/src/android/
jar/src/:/opt/android-sdk/platforms/android-22/android.jar -d .classes src/org/qtproject/qt5/android/accessibility/QtAccessibilityDelegate.java src/org/qtproject/qt5/android/accessibility/QtNativeAccessibility.ja
va src/org/qtproject/qt5/android/QtActivityDelegate.java src/org/qtproject/qt5/android/QtEditText.java src/org/qtproject/qt5/android/QtInputConnection.java src/org/qtproject/qt5/android/QtLayout.java src/org/qtpr
oject/qt5/android/QtMessageDialogHelper.java src/org/qtproject/qt5/android/QtNative.java src/org/qtproject/qt5/android/QtNativeLibrariesDir.java src/org/qtproject/qt5/android/QtSurface.java src/org/qtproject/qt5/
android/ExtractStyle.java src/org/qtproject/qt5/android/EditContextView.java src/org/qtproject/qt5/android/EditPopupMenu.java src/org/qtproject/qt5/android/CursorHandle.java src/org/qtproject/qt5/android/QtThread
.java                                                                                                                                                                                                               
make[4]: javac: Command not found                                                                                                                                                                                   
make[4]: *** [Makefile:292: .classes] Error 127                                                                                                                                                                     
make[4]: Leaving directory '/tmp/yaourt-tmp-patrick/aur-android-armv7a-eabi-qt5/src/qt-everywhere-src-5.12.1/qtbase/src/android/jar'                                                                                
make[3]: *** [Makefile:49: sub-jar-make_first-ordered] Error 2                                                                                                                                                      
make[3]: Leaving directory '/tmp/yaourt-tmp-patrick/aur-android-armv7a-eabi-qt5/src/qt-everywhere-src-5.12.1/qtbase/src/android'                                                                                    
make[2]: *** [Makefile:777: sub--tmp-yaourt-tmp-patrick-aur-android-armv7a-eabi-qt5-src-qt-everywhere-src-5-12-1-qtbase-src-android-make_first] Error 2                                                             
make[2]: *** Waiting for unfinished jobs....                                                                                                                                                                        
compiling src/pcre2_ord2utf.c                                                                                                                                                                                       
compiling src/pcre2_pattern_info.c                                                                                                                                                                                  
compiling src/pcre2_serialize.c                                                                                                                                                                                     
compiling src/pcre2_string_utils.c                                                                                                                                                                                  
compiling src/pcre2_study.c                                                                                                                                                                                         
compiling src/pcre2_substitute.c      

A package for javac is missing, probably java-environment-common

@luntik2012 The compiler is provided by the Android NDK. However, the latest version only ships Clang anymore (someone please correct me if I'm wrong). The cool thing about Clang is that one build of it can build for all target platforms (which can be specified via a command line option). It could be that the Qt Creator integration for this way of building is not available yet. Maybe it helps to build a "standalone toolchain" (see https://developer.android.com/ndk/guides/standalone_toolchain) to avoid that problem.

But I haven't tested that yet. I personally use CMake (rather than qmake) and invoke it directly on the command line like this: https://github.com/Martchus/passwordmanager#concrete-example-of-3-for-building-an-android-apk-under-arch-linux

Then I open the project in Qt Creator and select the build directory I executed the CMake command manually in. That works more or less. I haven't done any fancy stuff like debugging within Qt Creator, though. And for making the APK and deploying it I also rely on CMake targets (which of course can be easily triggered via Qt Creator).