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

Git Clone URL: https://aur.archlinux.org/android-qt5-armeabi-v7a.git (read-only)
Package Base: android-qt5-armeabi-v7a
Description: Qt 5 for Android
Upstream URL: https://www.qt.io
Licenses: GPL3, LGPL
Groups: android-qt5
Submitter: hipersayan_x
Maintainer: hipersayan_x
Last Packager: hipersayan_x
Votes: 4
Popularity: 0.235481
First Submitted: 2016-02-29 14:37
Last Updated: 2016-06-25 14:33

Dependencies (17)

Required by (0)

Sources (5)

Latest Comments

hipersayan_x commented on 2016-06-23 15:37

Fixed, thanks!

morgoth_bauglir commented on 2016-06-23 15:00

Getting an error on the download of qt-everywhere: http://hastebin.com/cewiyohere.coffee

hipersayan_x commented on 2016-04-17 16:16

I added a function to check the latest version in all folders, thanks :)

nslxndr commented on 2016-04-17 15:01

Makefile:9824: recipe for target '.obj/qxml.o' failed
make[3]: *** [.obj/qxml.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory '/tmp/makepkg/android-qt5-armeabi-v7a/src/qt-everywhere-opensource-src-5.6.0/qtbase/src/tools/bootstrap'
Makefile:90: recipe for target 'sub-bootstrap-make_first' failed
make[2]: *** [sub-bootstrap-make_first] Error 2
make[2]: Leaving directory '/tmp/makepkg/android-qt5-armeabi-v7a/src/qt-everywhere-opensource-src-5.6.0/qtbase/src'
Makefile:45: recipe for target 'sub-src-make_first' failed
make[1]: *** [sub-src-make_first] Error 2
make[1]: Leaving directory '/tmp/makepkg/android-qt5-armeabi-v7a/src/qt-everywhere-opensource-src-5.6.0/qtbase'
Makefile:69: recipe for target 'module-qtbase-make_first' failed
make: *** [module-qtbase-make_first] Error 2
==> ERROR: A failure occurred in build().
Aborting...

I have
- android-platform and android-platform-17,
- android-sdk-build-tools and android-sdk-build-tools-17
both revisions installed, so:
- ANDROID_BUILD_TOOLS_REVISION="17.0.0 23.0.3"
- ANDROID_API_VERSION="android-17 android-23"

My suggestion from my previous comment is a general purpose which solves the problem:
diff --git a/PKGBUILD b/PKGBUILD
index 3f0996c..62ace8b 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -106,8 +106,8 @@ build() {

export ANDROID_NDK_ROOT=/opt/android-ndk
export ANDROID_SDK_ROOT=/opt/android-sdk
- export ANDROID_BUILD_TOOLS_REVISION=$(ls ${ANDROID_SDK_ROOT}/build-tools)
- export ANDROID_API_VERSION=$(ls ${ANDROID_SDK_ROOT}/platforms)
+ export ANDROID_BUILD_TOOLS_REVISION=$(ls ${ANDROID_SDK_ROOT}/build-tools | tail -1)
+ export ANDROID_API_VERSION=$(ls ${ANDROID_SDK_ROOT}/platforms | tail -1)
export PYTHON=/usr/bin/python2

ndkPlatform=$(ls ${ANDROID_NDK_ROOT}/platforms | sort -V | tail -n 1)

hipersayan_x commented on 2016-04-15 16:25

Updated scripts. Using latest version of the SDK and NDK by default, also this time patches are applied depending on the platform.

nslxndr commented on 2016-04-14 06:11

Because can be installed any revision of android-sdk-build-tools from 17 to 23.0.3 (one or more), I think is a better solution to get the highest installed version:
ls $ANDROID_HOME/build-tools/ | tail -1
But there is probably still a better solution.

hipersayan_x commented on 2016-04-13 23:37

Probably can be detected with "ls /opt/android-sdk/build-tools", but not sure if it is the best solution. Thanks for letting me know :)

haffmans commented on 2016-04-13 20:54

Compilation fails quite early on if you have a different version of android-sdk-build-tools installed than 23.0.2 (see export ANDROID_BUILD_TOOLS_REVISION line in the PKGBUILD). The current version on AUR is android-sdk-build-tools r23.0.3-1. It took me a while to figure out what was wrong, due to the verbosity of the build.

Would it make sense to pin to a specific version in the PKGBUILD or somehow detect the installed revision properly? It might save a few headaches :)

wicast commented on 2016-02-25 15:33

Never mind(separate package is acceptable for me.

hipersayan_x commented on 2016-02-25 13:35

wicast, compiling Qt takes a long time, compiling Qt for 3 or more architectures in the same package will take a lot of hours and requires a lot of disk space, it's much better to create one package for each architecture and let user decide which architectures it want to install.

All comments