Feature Request: STAND with support for CMAKE /w NDK

[ArtificialRaccoon]

STAND appears to have been built around supporting autotools for building various libraries in BAD. This works fine for many components, but the following have since abandoned autotools for CMAKE:

GEOS (3.10 and later only support CMAKE)
GDAL (3.6.0 only supports CMAKE)
PROJ (Post 8.2.1 only supports CMAKE)

When building with CMAKE (and targeting Android), you need to specify the NDK toolchain file using the following parameters:

    -DCMAKE_TOOLCHAIN_FILE=${NDK_ROOT}/build/cmake/android.toolchain.cmake \
    -DANDROID_NDK=${NDK_ROOT}                               \
    -DANDROID_ABI=armeabi-v7a                               \
    -DANDROID_PLATFORM=android-19                           \
    -DANDROID_STL=c++_shared                                \
    -DCMAKE_LIBRARY_OUTPUT_DIRECTORY=${LIB1_DIRECTORY}/libs/armeabi-v7a       \
    ${LIB1_DIRECTORY}

STAND appears to not include the toolchain file, and the NDK directory structure appears to be laid out differently than the source archive (android-ndk-r23c-linux.zip).

Would it be possible to build a set of STAND images which support CMAKE?

[rhardih]

It's a bit cumbersome, because it needs special casing in the make files on a per version basis, but it's definitely doable. Case in point, Tesseract 4.0.0 is using CMake whilst earlier versions are Autotools.

Autotools: https://github.com/rhardih/bad/blob/master/tesseract/tesseract-3.05.02.Dockerfile
CMake: https://github.com/rhardih/bad/blob/master/tesseract/tesseract-4.0.0.Dockerfile

I wonder if there's a more generic approach to lay out the makefiles and maintain different docker images depending on which build system to use. 🤔