Closed matspetter closed 6 years ago
./configure is needed to create, for most projects, extra files that are not contained in the original archive of the project.
Also in some cases small adaptions need to be made.
Which './configure' command is used (when used at all) and the needed adaptions are placed in the corresponding .mk file
# ./configure --enable-rttopo --enable-gcp --enable-examples=no --build=x86_64-pc-linux-gnu --host=arm-linux-eabi
...
# -------------------
# Excluded files:
...
# comment out TARGET_CPU in config.h - will be replaced with TARGET_ARCH_ABI
I will commit the present status (where Spatialite has been updated i.e. not rasterlite2) when the 3 build have run
armeabi-v7a arm64-v8a x86_64
I have pushed of all the added/changed files
By then the [x86_64] Compile is now completed
A summery of the Spatialite project can be seen here: https://github.com/geopaparazzi/libjsqlite-spatialite-android/wiki/Android_4.5.0.mk
The created libraries have been uploaded, and the link updated.
Would it be possible to check-in the results of your configure (and autoconf) runs into the repo? In that way it would be much easier to build the whole thing from sources.
If not, maybe have a master script on top level that runs configure for each needed sub-library with the correct parameters (== the parameters you are using).