Support: clear out some of the scripts

Remove the Docker image creation rules (Dockerfile) for the CircleCI
docker image. The image has been unmaintained for long enough that it is
not valuable any longer. Furthermore, with the migration to GitHub
actions, the image is no longer something we need to construct as GitHub
provides the image.

The helper scripts that were only in use for the Docker image can also
be removed. The only script here that is potentially of particular
interest is the `prepare-android-ndk.py` which is, in effect, a
specialised invocation of `curl`.

Author: compnerd

.circleci/config.yml

@@ -28,17 +28,6 @@ test_step: &test_step
     name: Test
     command: cd build && ../Support/Scripts/run-${DEBUGGER-lldb}-tests.sh --log
 
-check_dirty_step: &check_dirty_step
-  run:
-    name: Check for dirty state
-    command: git --no-pager diff --exit-code
-
-start_android_emulator_step: &start_android_emulator_step
-  run:
-    name: Start Android emulator
-    command: ./Support/Scripts/start-android-emulator.py --target ${TARGET}
-    background: true
-
 build_only_defaults: &build_only_defaults
   <<: *docker_config
   steps:
@@ -54,15 +43,6 @@ build_and_test_defaults: &build_and_test_defaults
     - *build_step
     - *test_step
 
-build_and_test_android: &build_and_test_android
-  <<: *docker_config
-  steps:
-    - checkout
-    - *configure_step
-    - *build_step
-    - *start_android_emulator_step
-    - *test_step
-
 version: 2
 jobs:
   Linux-X86-Clang:
@@ -91,18 +71,6 @@ jobs:
       TARGET: Linux-X86_64-Clang
       DEBUGGER: gdb
       GDB_TESTS: "gdb.base/break;gdb.base/printcmds;gdb.base/step-bt"
-  Android-ARM:
-    <<: *build_and_test_android
-    environment:
-      PLATFORM: 1
-      TARGET: Android-ARM
-      EXTRA_CMAKE_ARGS: "-DCMAKE_SYSTEM_VERSION=21"
-  Android-ARM64:
-    <<: *build_and_test_android
-    environment:
-      PLATFORM: 1
-      TARGET: Android-ARM64
-      EXTRA_CMAKE_ARGS: "-DCMAKE_SYSTEM_VERSION=24"
   Tizen-X86:
     <<: *build_only_defaults
   Tizen-ARM:
@@ -118,8 +86,5 @@ workflows:
       - Linux-X86_64-Clang-platform
       - Linux-X86_64-GDB
       - Linux-X86_64-GDB-Clang
-      - Android-ARM
-      - Android-ARM-16
-      - Android-ARM64
       - Tizen-X86
       - Tizen-ARM

README.md

@@ -41,30 +41,15 @@ ninja -C out
 ### Compiling for Android
 
 For Android native debugging, it is possible to build ds2 with the Android NDK.
-A script is provided to download the Android NDK automatically for you.
-
-`Support/Scripts/prepare-android-ndk.py` will download a working version
-of the NDK, extract it, and install it to `/tmp/android-ndk`.
 
 ```sh
-cd ds2
-./Support/Scripts/prepare-android-ndk.py
-mkdir build && cd build
-cmake -DCMAKE_TOOLCHAIN_FILE=../Support/CMake/Toolchain-Android-ARM.cmake ..
-make
+cmake -B out -D CMAKE_SYSTEM_NAME=Android -D CMAKE_ANDROID_ARCH_ABI=armeabi-v7a -G Ninja -S ds2
+ninja -C out
 ```
 
 Note that this will build ds2 targeting the highest level API level that the
 NDK supports. If you want to target another api level, e.g. 21, add the flag
-`-DCMAKE_SYSTEM_VERSION=21` to your cmake invocation.
-
-#### Testing on Android device
-
-If you would like to use ds2 to run tests in the LLDB test suite using an
-Android device, you should use the script
-`Support/Scripts/prepare-android-ndk.py` to get a checkout of the android NDK.
-The LLDB test suite expects an NDK to exist on your host, and that script will
-download and unpack it where the CMake Toolchain files expect it to be.
+`-DCMAKE_SYSTEM_VERSION=21` to your CMake invocation.
 
 ### Compiling for Linux ARM