build.sh

#!/bin/bash 
# <---IMPORTANT NOTE! if you dont have
# termux-exec package installed, that line needs to be:
# #!$PREFIX/bin/bash

# This guy simply prevents the chain of events from
# continuing idiotically, if one step fails. The script
# will stop there.
function catch_error() {
  local error_code="$?"
  echo "Error: $error_code"
}
trap catch_error ERR
set -e


# You may need to change this if you found the need
# to locate your project files outside the hierarchy
# of the termux 'home' dir
dir=$PWD/$*
echo "Work Dir: $dir"

if [ ! -d "$dir" ]; then
  echo "Directory does not exist"; exit 1;
else
  echo "Directory exists, continuing..."; fi

cd $dir

#its likely these arent executable at first download
chmod a+x toolz/*

export JAVA_HOME="$PREFIX/opt/openjdk"
export PATH="$PATH:$JAVA_HOME/bin"
export BUILD_TOOLS="$dir/toolz"
export PATH="$BUILD_TOOLS:$PATH"

# Clean up junk from last build:
rm -rf build
mkdir build
mkdir build/classes

# Begin compilation!

echo "---------------aapt2: "
aapt2 compile -v\
  --dir res \
  -o build/resources.zip 2>&1 \
  | sed -E 's/(E|e)rror/\x1b[31merror\x1b[0m/g'

# -I gives the path to the android platform’s android.jar,
# --manifest specifies the android manifest,
# --java specifies the path to generate the R.java file.
# --o specifies the output path.

#eventually we may use shared libs, and this is
#the start of how that would happen. google makes
#using appcompat an endless moving target with no
#explanation and impossible-to-locate jars,  so were
#skipping it for now. the appcompat libs are in this
#dir but are unlinked so dont end up in the build:
##  --shared-lib libs/*.jar \
#  -I libs/android-support-v4.jar \


aapt2 link -v  \
  -A assets/ \
  -I toolz/android.jar \
  --manifest AndroidManifest.xml \
  --java build/ \
  -o build/link.apk \
   build/resources.zip \
   --auto-add-overlay 2>&1 \
    | sed -E 's/(E|e)rror/\x1b[31merror\x1b[0m/g'

# This will compile our code to java bytecode
# and place the .class files in build/classes
# directory. Take note of the R.java file which
# is the one that was generated in the previous step.
# Without --release=8 nothing will work and
# puppies will die
# filter:trim path from android.jar
# sed -E 's/.*\/([^/]*\.class).*/\[android.jar\]\-\-\-\>\ \1/'
# filter: 'error' in red:
# sed -E 's/error/\x1b[31merror\x1b[0m/g'
# filter: trim (some) java paths:
# sed -E 's/(*.\/java.base\/java\/)(.*)(\])/\2/'


echo "---------------- Using `$JAVA_HOME/bin/javac --version` ---------------"
$JAVA_HOME/bin/javac --release=8 -verbose \
 -d build/classes \
    --class-path toolz/android.jar \
 src/com/hellogpt/MainActivity.java \
 build/com/hellogpt/R.java 2>&1 \
  | sed -E -e 's/.*\/([^/]*\.class).*/\[android.jar\]\-\-\-\>\ \1/' \
-e 's/(E|e)rror/\x1b[31merror\x1b[0m/g' \
-e 's/(.*\/java.base\/java\/)(.*)(\])/\[java 8\]\-\-\-\-\>\ \2/'


# Once we have java bytecode we now convert it to
# DEX bytecode that runs on android devices.
# This is done using android’s d8 commandline tool.

# d8 uses '/bin/ls' which is not where it is, in termux.
# this..i found out you could get termux-ready versions of
# both these tools so these arent being used anymore.
#sed -i 's/\/bin\/ls/ls/g' $BUILD_TOOLS/dx
#sed -i 's/\/bin\/ls/ls/g' $BUILD_TOOLS/d8

# IF you dont include that 'cd' below, the fails will be monumental.
# it took me 60% of the time i spent on this to figure out
# that this tool WILL NOT FUNCTION unless the directory structure
# matches the package name, ie com/hellogpt com.hellogpt.
# if it even catches a glimpse that its actually src/com/hellogpt
# itll uncompromisingly refuse to communicate or function

# To convert into dex :
echo "---------------d8: "
cd $dir/build/classes
dx --dex --verbose --debug --min-sdk-version=26\
                 --output=classes.dex \
                com/hellogpt/*.class \

# This is the same step as above (you only need
# but one of them) but uses d8 instead of dx.
# I chose dx only because its debug output is better
# (d8 is completely silent and impossible to troubleshoot,
# however in the end I got them both to work.)
#$BUILD_TOOLS/d8 --classpath $ANDROID_HOME/platforms/$TARGET_PLATFORM/android.jar \
#       --output build/dex/ \
#       $(ls -1 build/classes/com/hellogpt |\
#        xargs -I{} printf "%s "\
#        "build/classes/com/hellogpt/{}")


# The output will be a file called classes.dex.
# We then need to add this file into our link.apk
# that was generated in the linking stage:
# (notice that zip comes from your system and isn't
# in android sdk):

echo "---------------zip: "
zip -v -u ../link.apk classes.dex


# Next we need to zip align our apk using the
# zipalign tool and then sign the apk using the
# apksigner tool.

echo "---------------zipalign: "
$BUILD_TOOLS/zipalign -v -f -p 4 ../link.apk ../zipout.apk

# (To sign the application you will need to have a
# public-private key pair. You can generate one
# using java’s keytool. This you only do once, so
# if its your first time thru, uncomment the 'keytool'
# line and answer the questions:
# I used 'password' when asked for one, see below:
#keytool -genkeypair -keystore key.keystore -keyalg RSA


# And sign! --ks-pass pass:<YOUR PASS HERE> if you change it.
echo "---------------apksigner: "
$BUILD_TOOLS/apksigner sign \
  --verbose \
  --ks $dir/key.keystore \
  --ks-pass pass:password \
  --out ../final.apk ../zipout.apk

# The output of this is apk: final.apk.
echo
echo
echo "...if success, result is $dir/build/final.apk"