prefix tags in android images with ndk, sdk and os

[Emilgardis]

Checklist

• I've looked through the issues and pull requests for similar request
• This feature could be solved with a custom docker image (optional)

Describe your request

We should consider if we should rename the android images to *-linux-androideabi:ndkxxy-sdkxx-osxx-<branch>

Describe why this would be a good inclusion for cross

This would mean less confusion about what is included, and make it easier to maintain multiple versions without much effort (as build-docker-image could inject it for you`

[Emilgardis]

I do think it's worth it to keep a simple :main/vx.y.z tag, but on top of that we could provide extra tags

[Alexhuszagh]

Would we then do multiple deployments, or a single deployment? If so, I think we only would need 1 NDK version (the latest, or r25b right now) and then 1 version at each major version. If we do the latter, we would ideally use our targets.toml to specify the versions. If not, we probably still need a single entry in targets.toml just so we don't hard-code it build-docker-image.

[berendsliedrecht]

Hi, I am running into the same issues specified in #1195. Right now I wanted to fix it by passing ANDROID_NDK as an environment variable and I hoped the image would pick it up. Would something like that not be an easier solution? I think if we let users pass in the ndk/sdk/etc. versions from env vars there is no need for an infinite amount of images, right?

Maybe something like this:

[target.armv7-linux-androideabi]
image = "ghcr.io/cross-rs/armv7-linux-androideabi:main"
build-args = ["ANDROID_NDK=r24", "ANDROID_SDK=21", "ANDROID_VERSION=5.0.0_r1"]

[Emilgardis]

I dont think we should have multiple ndks in an image, that would be a huge image and take an imense amount of CI time in one step. What we could do is allow something similar where if you dont provide an explicit image, cross recognizes the env var ANDROID_NDK etc and uses the appropriate image if it exists