fdroidserver/buildserver/provision-android-ndk

#!/bin/bash
#

echo $0
set -e
set -x

NDK_BASE=$1

test -e $NDK_BASE || mkdir -p $NDK_BASE
cd $NDK_BASE

if [ ! -e $NDK_BASE/r10e ]; then
    7zr x /vagrant/cache/android-ndk-r10e-linux-x86_64.bin > /dev/null
    mv android-ndk-r10e r10e
fi

for version in r21e r22b; do
    if [ ! -e ${NDK_BASE}/${version} ]; then
        unzip /vagrant/cache/android-ndk-${version}-linux-x86_64.zip > /dev/null
        mv android-ndk-${version} ${version}
    fi
done

chmod -R a+rX $NDK_BASE/
find $NDK_BASE/ -type f -executable -print0 | xargs -0 chmod a+x
buildserver: unpack NDK with a provisioning shell script This makes the process closer to ./jenkins-build scripts and .gitlab-ci.yml files. Hopefully it uses less RAM than chef too. 2016-06-15 15:02:37 +02:00			`#!/bin/bash`
			`#`

buildserver: make provision scripts output name to log 2016-07-04 14:20:42 +02:00			`echo $0`
buildserver: unpack NDK with a provisioning shell script This makes the process closer to ./jenkins-build scripts and .gitlab-ci.yml files. Hopefully it uses less RAM than chef too. 2016-06-15 15:02:37 +02:00			`set -e`
provision-ndk: set -x to see what it currently does 2018-11-28 20:46:44 +01:00			`set -x`
buildserver: unpack NDK with a provisioning shell script This makes the process closer to ./jenkins-build scripts and .gitlab-ci.yml files. Hopefully it uses less RAM than chef too. 2016-06-15 15:02:37 +02:00
buildserver: do not set NDK env vars, they are handled by `fdroid build` `fdroid build` handles setting the NDK env vars since the NDK version can change depending on the app being build. Unlike ANDROID_HOME, there is no single global NDK location. The NDK installs are all versioned. 2016-06-17 11:29:00 +02:00			`NDK_BASE=$1`
buildserver: unpack NDK with a provisioning shell script This makes the process closer to ./jenkins-build scripts and .gitlab-ci.yml files. Hopefully it uses less RAM than chef too. 2016-06-15 15:02:37 +02:00
buildserver: do not set NDK env vars, they are handled by `fdroid build` `fdroid build` handles setting the NDK env vars since the NDK version can change depending on the app being build. Unlike ANDROID_HOME, there is no single global NDK location. The NDK installs are all versioned. 2016-06-17 11:29:00 +02:00			`test -e $NDK_BASE \|\| mkdir -p $NDK_BASE`
			`cd $NDK_BASE`
buildserver: unpack NDK with a provisioning shell script This makes the process closer to ./jenkins-build scripts and .gitlab-ci.yml files. Hopefully it uses less RAM than chef too. 2016-06-15 15:02:37 +02:00
buildserver: do not set NDK env vars, they are handled by `fdroid build` `fdroid build` handles setting the NDK env vars since the NDK version can change depending on the app being build. Unlike ANDROID_HOME, there is no single global NDK location. The NDK installs are all versioned. 2016-06-17 11:29:00 +02:00			`if [ ! -e $NDK_BASE/r10e ]; then`
all: remove 32-bit buildserver code We dropped support for 32-bit, so remove all the now unused code and references. 2016-07-13 17:47:58 +02:00			`7zr x /vagrant/cache/android-ndk-r10e-linux-x86_64.bin > /dev/null`
buildserver: unpack NDK with a provisioning shell script This makes the process closer to ./jenkins-build scripts and .gitlab-ci.yml files. Hopefully it uses less RAM than chef too. 2016-06-15 15:02:37 +02:00			`mv android-ndk-r10e r10e`
			`fi`

buildserver: trim pre-installed NDK list down to the bare minimum This keeps the Long Term Support release and the latest release installed. r10e was kept in because it needs a special extraction method, since it is a .bin file, not a .zip. r12b is kept in because it is the old default. Here is a survey of the NDK versions used in the most recent Builds entry in each app that uses the NDK: {'r10e': 6, 'r12b': 93, 'r13b': 4, 'r14b': 5, 'r15c': 7, 'r16b': 14, 'r17b': 4, 'r17c': 7, 'r18b': 9, 'r19c': 17, 'r20': 1, 'r20b': 22, 'r21': 3, 'r21d': 56, 'r21e': 65, 'r22': 9, 'r22b': 15, 'r9b': 1} #517 import glob import os import yaml try: from yaml import CSafeLoader as SafeLoader except ImportError: from yaml import SafeLoader ndks = dict() for f in glob.glob('metadata/*.yml'): with open(f) as fp: app = yaml.load(fp, Loader=SafeLoader) if app.get('Disable'): continue build = app.get('Builds', [])[-1] if build.get('disabled'): continue ndk = build.get('ndk') if ndk and ndk[1] == '9': print(f, build) elif ndk and int(ndk[2:3]) < 18: print(f, build) if ndk: print(f, ndk) if ndk not in ndks: ndks[ndk] = 0 ndks[ndk] += 1 import pprint pprint.pprint(ndks) 2021-05-12 15:04:24 +02:00			`for version in r21e r22b; do`
buildserver: support any recent NDK version, with stable filenames Now that the download file name and type seems to have stabilized, I think we no longer need to manually specify each new added release in this script to unpack. closes #331 2017-06-28 16:55:34 +02:00			`if [ ! -e ${NDK_BASE}/${version} ]; then`
			`unzip /vagrant/cache/android-ndk-${version}-linux-x86_64.zip > /dev/null`
			`mv android-ndk-${version} ${version}`
			`fi`
			`done`
makebuildserver: add NDK r15b 2017-07-04 10:44:25 +02:00
buildserver: do not set NDK env vars, they are handled by `fdroid build` `fdroid build` handles setting the NDK env vars since the NDK version can change depending on the app being build. Unlike ANDROID_HOME, there is no single global NDK location. The NDK installs are all versioned. 2016-06-17 11:29:00 +02:00			`chmod -R a+rX $NDK_BASE/`
			`find $NDK_BASE/ -type f -executable -print0 \| xargs -0 chmod a+x`