Fix compilation for Android targets

[tyranron]

Fixes #58

Additionally, reworks CI pipeline:

• runs checks for --target ${{ matrix.target }}
• switches to dtolnay/rust-toolchain action (actions-rs seems to be somewhat deprecated)

[alice-i-cecile]

merges on Bevy main repo are blocked until https://github.com/Nercury/android_logger-rs/pull/59 is merged and a new version of android_logger is published

• @mockersf

See bevyengine/bevy#6901 (comment) for an example failure.

[tyranron]

@alice-i-cecile you could have temporary pinpoint bevy to previous version like =0.11.1. No need to push maintainer this hard 😅

[Nercury]

Sorry about this, thanks for the fix.

[Nercury]

@tyranron can you help me maintain this? I don't have any project now that uses this crate, so I need someone who can at least be able to test if it builds.
And it's ok to ping me on gitgub.

[Nercury]

@tyranron Buld has failed :/

[mockersf]

@Nercury I tried fixing the failure in https://github.com/Nercury/android_logger-rs/pull/60

[tyranron]

@Nercury

@tyranron can you help me maintain this?

Yes. Please, add me to project maintainers and crate owners, and I'll polish the repo and code, along with the CI pipeline.

[Nercury]

Invites are sent both on github and on crates.io. Thanks for joining :)

[tyranron]

@Nercury thanks 🍻

[rib]

Btw @tyranron, @Nercury if you'd like; we'd be happy to host the android_logger repo under the rust-mobile organisation that we recently created to split out several repos from the rust-windowing organisation (ref: rust-mobile/ndk#372)

Current repos here include:

• ndk/ndk-sys
• cargo-apk
• cargo-subcommand
• android-activity (+ older ndk-glue + android-glue-rs)
• xbuild

You'd still be the owners/maintainers + would add you to the org.

One benefit would just be that it helps to collate more of the utility Rust crates that are helpful for mobile development in one discoverable place.

Another benefit might also be that it helps with pooling resources in case you do also want help with maintaining the project over time since there will be shared interests amongst the devs for the related projects.

[tyranron]

@rib thanks. I'd like to.

[rib]

I've just sent you and @Nercury an invite to the rust-mobile organisation. I think it would then be up to @Nercury to follow the instructions here: https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository for transferring a repo (I assume only @Nercury can do that as the owner of this repo)

[alice-i-cecile]

@alice-i-cecile you could have temporary pinpoint bevy to previous version like =0.11.1. No need to push maintainer this hard 😅

Yep, sorry to imply more pressure there! We had lots of other options (pin a version, use a fork, remove from CI), but wanted to let upstream know that they'd broken stuff <3

Thanks a ton for fixing this and making this tool!

[MarijnS95]

@Nercury @rib while not related to this PR: any progress on transferring the repo?

[rib]

I haven't heard back since I sent out the email inviting @Nercury and @tyranron, so not sure if @Nercury would be ok with transferring the repo to rust-mobile or not currently.

@tyranron said they would be happy to see the repo transferred (and they are a member of rust-mobile now), but it would need an OK from @Nercury to actually transfer the repo.