CI for android-support Crate
Is your feature request related to a problem? Please describe.
android-support crate, which is a core component for running the library on android application, is not a part of CI. With !31 (merged) being merged to the mainstream, it'll be our center of interest (along with our android client) with respect to the goals of this summer of code, as our majority of changes will target this crate as it provides custom implementation for the android application and is a kind of bridge that connects android application codebase and our rust library core(speaking technically, the FFI) and we'll be adding functions supported by core to it. Considering these facts, we need to track it in CI if it breaks at some point, otherwise if it goes unnoticed then we may get in a serious trouble, as android studio(AS) uses the latest cached version of
libirdestdroid.so in our case) created as lib on compiling the crate, if we don't re-compile the crate then we'll be using the older version of it, and if the latest version of crate doesn't build perfectly or to say clearly yields compilation errors then we won't be able to trace it, and application will work fine despite the existence of errors in
Describe the solution you'd like
Its build(compilation) should be checked each time changes are made to it or we push to the repository/create an MR to verify this crate is building green, like ~all other components of the codebase.
Describe alternatives you've considered
Writing a CI script for it and keeping track if it breaks at some point
PS: This'll be worked on after !31 (merged) is merged to the mainstream