Android CI

[numberZero]

Add Android CI. Mostly a copy from minetest_android_deps where Irrlicht was added before forking.

An alternative would be to use build.sh directly from that repo. But keeping the build script separate from own code makes little sense IMO. A better approach could be to only import _setup_toolchain to ensure compatibility but that requires some changes in the deps repo.

[numberZero]

Note: the CI passes on its own commit, a832635: https://github.com/numberZero/irrlicht/actions/runs/4778460794/jobs/8494894748. The failure is due to later changes in this repo (the “pull request” checks run on the merge result).

[numberZero]

Now that Android fixes are in master, this simply works. Didn’t test whether the Irrlicht the CI builds works too, though.

[sfan5]

Maybe we can just clone https://github.com/minetest/minetest_android_deps and run the build from there? I'm not too happy about so much duplication.

[numberZero]

Maybe we can just clone https://github.com/minetest/minetest_android_deps and run the build from there? I'm not too happy about so much duplication.

JPEG and PNG don’t need to be built here at all anymore as they’re available in the deps since luanti-org/luanti_android_deps#4. But for Irrlicht itself, it’d be rather awkward to keep the build script in a separate repository. For the environment setup it’s possible but copy it or import it, it will be fragile either way.

[sfan5]

I decided my opinion is wrong.