Confused exactly what this is

[Vixeliz]

I understand this can be used to build android apps on termux. I have a few questions. Firstly is it possible to add my own applications to build? Secondly would it be possible to build this? After the first build do you have to be connected to the internet to build an application? Sorry for the questions just not sure exactly what this project is and if it has a use besides the included apk build scripts.

[github-actions]

Thank you for contributing to make this project better😎 Keep up and follow to solve this issue.

[SDRausty]

I understand this can be used to build android apps on termux.

Yes, you can. Thousands of apps can be built at present.

I have a few questions. Firstly is it possible to add my own applications to build?

Yes, this is possible with this command:
build.one.sh

Secondly would it be possible to build this?

Yes, it is possible with this command:
build.repo.bash https://github.com/love2d/love-android

This project can still be greatly improved; Please consider creating a pull request; Here is the result of build.repo.bash https://github.com/love2d/love-android:

After the first build do you have to be connected to the internet to build an application?

No, an Internet connection is not required after the first build; Please enjoy 🎵 🎶

[Vixeliz]

Hmmm it seems that love does not build with this there are many errors. Is there any way to get a log to upload?

[Vixeliz]

Also thx you for this amazing project and the response!

[SDRausty]

love does not build

love should install with the command:
pc love

==> Running TermuxArch command pc love v2.0.1246...
resolving dependencies...
looking for conflicting packages...
warning: dependency cycle detected:
warning: mesa will be installed before its libglvnd dependency

Packages (40) alsa-lib-1.2.5.1-3  alsa-topology-conf-1.2.5.1-1
              alsa-ucm-conf-1.2.5.1-1  desktop-file-utils-0.26-1
              hidapi-0.10.1-1  libdrm-2.4.107-1  libglvnd-1.3.4-1
              libibus-1.5.25-3  libmodplug-0.8.9.0-3  libogg-1.3.5-1
              libomxil-bellagio-0.9.3-3  libpciaccess-0.16-2  libtheora-1.1.1-5
              libunwind-1.5.0-1  libusb-1.0.24-2  libvorbis-1.3.7-2
              libx11-1.7.2-1  libxau-1.0.9-3  libxcb-1.14-1  libxcursor-1.2.0-2
              libxdamage-1.1.5-3  libxdmcp-1.1.3-3  libxext-1.3.4-3
              libxfixes-6.0.0-1  libxrender-0.9.10-4  libxshmfence-1.3-2
              libxxf86vm-1.1.4-4  llvm-libs-12.0.1-4
              lm_sensors-1:3.6.0.r41.g31d1f125-1
              luajit-git-v2.1.0.beta3.r201.gdd5032ed-1  mesa-21.2.2-1
              mpg123-1.29.0-1  openal-1.21.1-1  sdl2-2.0.16-2
              shared-mime-info-2.0+57+gc1d1c70-1  vulkan-icd-loader-1.2.191-1
              wayland-1.19.0-1  xcb-proto-1.14.1-3  xorgproto-2021.5-1
              love-11.3-1

Total Download Size:    54.27 MiB
Total Installed Size:  303.36 MiB

:: Proceed with installation? [Y/n]

thx you for this amazing project and the response!

You are very welcome; I am amazed at how this project has developed over time. This would not be possible without contributors like you; Thank you!

[SDRausty]

love does not build

Or is this build.repo.bash https://github.com/qiushi123/love the one?

[Vixeliz]

Hello! Thx for the response again. Indeed love2d the first repo I put is the one I was wondering about. I am aware I could run via termuxarch but I would love to be able to build the apk for native use on android. Is the build failing due to the application using c/c++ code or it using gradle? Any help would be deeply appreciated

[SDRausty]

be able to build the apk for native use on android.

You are very welcome; What is the link to the APK source code?

[Vixeliz]

Https://github.com/love2d/love-android is for building it I believe. It doesn't actually build correctly

[Vixeliz]

Hello not trying to push at all i was just wondering if you had figured out why it wasn't building yet?

[SDRausty]

figured out why it wasn't building

It wants dependancies; This link has https://github.com/SDRausty/buildAPKs/issues?q=is%3Aissue+library more information about using libraries with BuildAPKs. Also please see files .conf/README.md and .conf/LIBAUTH about this topic too.

[SDRausty]

I would love to be able to build the apk for native use on android.

Ditto, Let us see if we can make it happen! We have successfully integrated libraries before.

[Vixeliz]

Ok if I understand correctly I need to go through the gradle file and find any dependencies? Also does it matter if love uses native c/c++ code?

[SDRausty]

I would love to be able to build the apk for native use on android.

Ditto, Let us see if we can make this happen with love too! We have successfully integrated libraries into projects before:
a) cat ~/buildAPKs/.conf/README.md ~/buildAPKs/.conf/LIBAUTH
b) https://github.com/BuildAPKs/buildAPKs/issues?q=is%3Aissue+library
c) https://github.com/SDRausty/buildAPKs/issues?q=is%3Aissue+library

[SDRausty]

Ok if I understand correctly I need to go through the gradle file and find any dependencies?

Yes, and also start with integrating appcompat:

-tail -4 ~/buildAPKs/var/lfhvar.txt
-https://mvnrepository.com/artifact/com.android.support/appcompat-v7
-https://mvnrepository.com/artifact/androidx.appcompat

-# lfhvar.txt EOF

Updated to:

grep mvn ~/buildAPKs/.conf/LIBAUTH
Adjust the paths to the prerequisites of the project in `LIBDIRPATH build.one.bash`.  You can populate the ~/buildAPKs/var/cache/lib directory from the https://mvnrepository.com website.  For example, this link https://mvnrepository.com/artifact/androidx.appcompat/appcompat has appcompat libraries that you can download into ~/buildAPKs/var/cache/lib for compiling inclusion.
https://mvnrepository.com/artifact/androidx.appcompat
https://mvnrepository.com/artifact/com.android.support/appcompat-v7
Adapte las rutas a los requisitos previos del proyecto en `LIBDIRPATH build.one.bash`.  Puede llenar el directorio ~/buildAPKs/var/cache/lib desde el sitio https://mvnrepository.com web. Por ejemplo, este enlace https://mvnrepository.com/artifact/androidx.appcompat/appcompat contiene bibliotecas appcompat que puede descargar en ~/buildAPKs/var/cache/lib para compilar la inclusión.
https://mvnrepository.com/artifact/androidx.appcompat
https://mvnrepository.com/artifact/com.android.support/appcompat-v7
Adaptez les chemins aux prérequis du projet dans `LIBDIRPATH build.one.bash`.  Vous pouvez remplir le répertoire ~/buildAPKs/var/cache/lib à partir du site https://mvnrepository.com Web. Par exemple, ce lien https://mvnrepository.com/artifact/androidx.appcompat/appcompat contient des bibliothèques appcompat que vous pouvez télécharger dans ~/buildAPKs/var/cache/lib pour compiler l'inclusion.
https://mvnrepository.com/artifact/androidx.appcompat
https://mvnrepository.com/artifact/com.android.support/appcompat-v7

[Vixeliz]

Ok I have done that and added androidx.multidex as it is in the app's build.gradle file however it doesn't appear to be any different

[Vixeliz]

After changing .conf/LIBAUTH to true and adding those lines no apks show up in the build folder which Ig could be a good sign?

[Vixeliz]

It appears no artifacts are being loaded despite being in /var/cache/lib. I have made sure LIBDIRPATH is set I believe

[SDRausty]

Also does it matter if love uses native c/c++ code?

Yes, love uses native code. You can enable native code into the APKs by running build.native.bash which should change 1 to 0 in file ~/buildAPKs/.conf/DOSO for you:

dx: done;  Making com.google.oboe.sample.1633385837.apk...
Searching for 'CMakeLists.txt' files in ~/buildAPKs/sources/github.com/love2d/love-android/love/src/jni/oboe/samples/parselib/src/main/; Please be patient...
Found 1 'CMakeLists.txt' file.
Processing ~/buildAPKs/sources/github.com/love2d/love-android/love/src/jni/oboe/samples/parselib/src/main/cpp/CMakeLists.txt.
Beginning cmake and make in ~/buildAPKs/sources/github.com/love2d/love-android/love/src/jni/oboe/samples/parselib/src/main/output/lib/armeabi-v7a:
-- The C compiler identification is Clang 11.1.0
-- The CXX compiler identification is Clang 11.1.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /data/data/com.termux/files/usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /data/data/com.termux/files/usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
-- Build files have been written to: /data/data/com.termux/files/home/buildAPKs/sources/github.com/love2d/love-android/love/src/jni/oboe/samples/parselib/src/main/output/lib/armeabi-v7a
Scanning dependencies of target parselib
[ 11%] Building CXX object CMakeFiles/parselib.dir/stream/FileInputStream.cpp.o
[ 22%] Building CXX object CMakeFiles/parselib.dir/stream/InputStream.cpp.o
[ 33%] Building CXX object CMakeFiles/parselib.dir/stream/MemInputStream.cpp.o
[ 44%] Building CXX object CMakeFiles/parselib.dir/wav/AudioEncoding.cpp.o
[ 55%] Building CXX object CMakeFiles/parselib.dir/wav/WavChunkHeader.cpp.o
[ 66%] Building CXX object CMakeFiles/parselib.dir/wav/WavFmtChunkHeader.cpp.o
[ 77%] Building CXX object CMakeFiles/parselib.dir/wav/WavRIFFChunkHeader.cpp.o
[ 88%] Building CXX object CMakeFiles/parselib.dir/wav/WavStreamReader.cpp.o
[100%] Linking CXX static library libparselib.a
[100%] Built target parselib
Finished cmake and make in ~/buildAPKs/sources/github.com/love2d/love-android/love/src/jni/oboe/samples/parselib/src/main/output/lib/armeabi-v7a/.
No 'Android.mk' files were found: Continuing...
No 'jni' directory found: Continuing...
Adding classes.dex  to com.google.oboe.sample.1633385837.apk...
 'classes.dex'...
Signing com.google.oboe.sample.1633385837.apk: DONE

[Vixeliz]

Ok yes I have done that still no luck though. As said no artifacts being loaded ;-;

[Vixeliz]

It says this

aapt: done;  dalvikvm: begun...
Signal generated dalvikvm build.one.bash build.one.bash: EXITING...
buildAPKs signal 220 received by build.one.bash in /data/data/com.termux/files/home/buildAPKs/sources/native2/bitmap-plasma/app/src/main by build.one.bash.  More information in `/data/data/com.termux/files/home/buildAPKs/var/log/stnderr.native2.log` file.

Running: VAR="$(grep -C 2 -ie error -ie errors "/data/data/com.termux/files/home/buildAPKs/var/log/stnderr.native2.log")" && VAR="$(grep -v \-\- <<< $VAR)" && head <<< $VAR && tail <<< $VAR

[Vixeliz]

Ok I fixed that issue I think

[Vixeliz]

Still not building quite right though

[Vixeliz]

It appears it needs android.annotation and org.libsdl

[SDRausty]

It appears it needs android.annotation and org.libsdl

These want to be added as well.

[Vixeliz]

So do I add them to the file in /var/lfhvar.txt

[SDRausty]

Ok I have done that and added androidx.multidex as it is in the app's build.gradle file however it doesn't appear to be any different
It appears it needs android.annotation and org.libsdl

How would you download these files using curl from mvnrepository.com?

So do I add them to the file in /var/lfhvar.txt

The jars should be placed here:

~ $ tree ~/buildAPKs/var/cache/lib
/data/data/com.termux/files/home/buildAPKs/var/cache/lib
├── res-appcompat
├── res-cardview
├── res-design
└── res-recyclerview

4 directories, 0 files
~ $ grep LIBDIR ~/buildAPKs/bin/build.one.bash
        LIBDIRPATH=("$JDR/lib" "$JDR/libraries" "$JDR/library" "$JDR/libs" "$RDR/var/cache/lib") # modify array LIBDIRPATH to suit the projects artifact needs.
        for LIBDIR in ${LIBDIRPATH[@]} # every element in array LIBDIRPATH
                if [[ -d "$LIBDIR" ]] # library directory exists
                        DIRLIS="$(find -L "$LIBDIR" -type f -name "*.jar" 2>/dev/null)" || _PRINTSGE_ DIRLIS
                        printf "\\e[1;34m%s" "Adding $NUMIA artifacts and libraries from directory $LIBDIR into build ${PWD##*/} : "

This reference should also aid in our work here:
#1

[SDRausty]

solve with buildAPKs

YES
CORRECT

[github-actions]

old issue sanse activity message