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.

Don't worry about it, and thank you for your work on this package. I'm using the Qt 5.15 multi ABI from the official installer now, and I guess I will keep using that in the future.

I wish Qt6 would be an option, but let's face it, even the 6.2 is missing so many core things, and making so many incompatible changes... It's really fup what they did stopping support for Qt5 while Qt6 is nowhere near usable (unless you're doing pure Qt Widget and nothing else).

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.

@Martchus yes, I thought that same, I was about to change the sources to https://invent.kde.org/qt/qt/qt5.git, but cloning the entire repository with all its submodules is slow af, and it's not possible to just download a tarball because it won't download the submodules. Imagine cloning the repository every time for each architecture, is absurd.

It would theoretically make sense to update this package to include patches from KDE like the regular qt5-base package and mingw-w64-qt5-base. These patches contain a fix the issue. (However, I wasn't able to use this successfully since they introduced building for multiple archs in one go so I'm currently stuck with an older version and don't care anymore. I'm hoping android-aarch64-qt6-* packages will eventually work better.)

@MichaelS I think you simply need to downgrade to gcc 10 to build Qt

Compiling fails with following error:

android-aarch64-qt5/src/qt-everywhere-src-5.15.2/qtbase/include/QtCore/../../src/corelib/global/qendian.h:333:30: Fehler: »std::numeric_limits« ist kein Template 333 | { return QSpecialInteger(std::numeric_limits<T>::min()); }

Some ideas who to fix this problem?

Regards

Michael

At least the switch to CMake seems to ease cross compilation and makes Qt's build less odd compared to other projects. Whether androiddeployqt will work nicely is of course a different story and I haven't tested it yet. That's mainly because Qt 6 is so far quite limited, e.g. kirigami hasn't been ported yet. (By the way, with Qt 6 androiddeployqt is now part of the regular qt6-base package since we don't need to build such tools anymore for each target.)

@feedc0de will check, I hadn't time to update the package. @Martchus with latest Qt moves I don't trust it much now :-/

I was able to build 5.15.1 with the version found on my GitHub. However, in the end it was unusable with CMake (without taking a lot of extra effort) so I had to revert to 5.13.1 which seems to be the last good Qt 5 version for Android: https://github.com/Martchus/PKGBUILDs/commit/8bcbcdde529c4f5cc9f57091d91ad4927cb3f912
So I wouldn't get my hopes up that this will work nicely.

Btw, I have already added android-aarch64-qt6-base but not really tested it much besides from compiling it. Maybe Qt 6 will work better for our packaging approach.

When I try to make this pkg, my compilation fails:

compiling moc.cpp                                                                                                                                                                                                         (4 results) [38/559]
compiling customwidgetsinfo.cpp            
compiling main.cpp                     
compiling provider.cpp
error: Source option 6 is no longer supported. Use 7 or later.
error: Target option 6 is no longer supported. Use 7 or later.
make[3]: *** [Makefile:305: .classes] Fehler 2                                                                                                                                                                                                
make[3]: Verzeichnis „/tmp/trizen-feedc0de/android-aarch64-qt5/src/qt-everywhere-src-5.15.1/qtbase/src/network/android/jar“ wird verlassen
make[2]: *** [Makefile:303: sub-network-android-jar-make_first] Fehler 2                                                                                                                                                                      
make[2]: *** Es wird auf noch nicht beendete Prozesse gewartet....
compiling preprocessor.cpp                                                                                                                                                                                                                    
error: Source option 6 is no longer supported. Use 7 or later.                                                        
error: Target option 6 is no longer supported. Use 7 or later.
make[4]: *** [Makefile:334: .classes] Fehler 2                                                                         
make[4]: Verzeichnis „/tmp/trizen-feedc0de/android-aarch64-qt5/src/qt-everywhere-src-5.15.1/qtbase/src/android/jar“ wird verlassen
make[3]: *** [Makefile:49: sub-jar-make_first-ordered] Fehler 2
make[3]: Verzeichnis „/tmp/trizen-feedc0de/android-aarch64-qt5/src/qt-everywhere-src-5.15.1/qtbase/src/android“ wird verlassen
make[2]: *** [Makefile:801: sub--tmp-trizen-feedc0de-android-aarch64-qt5-src-qt-everywhere-src-5-15-1-qtbase-src-android-make_first] Fehler 2

a quick google search tells me it has to do with maven, but I have no idea what to change or why it happens.