You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
Cross-compiling to Android is quite tricky because of libusb-sys. paritytech/libusb-sys#4 fixed the fact that we were in reality compiling for Linux when trying to compile libusb for Android.
Right now on Android we are building libusb manually, but in order to do so we apply a patch on the source code, which is extremely hacky.
Libusb on Android seems to have quite a few runtime issues as well.
A final solution is to remove the dependency on libusb on Android. This is probably the most simple solution, and the one I would suggest. Nobody uses our Android build yet, so we won't break anything.
I'm opening this issue to gather opinion. Any comment on this?
Cross-compiling to Android is quite tricky because of libusb-sys.
paritytech/libusb-sys#4 fixed the fact that we were in reality compiling for Linux when trying to compile libusb for Android.
However this unveiled the problem that libusb actually doesn't support Android that well: https://github.com/paritytech/libusb-sys/blob/4418e92c82509d1f049f7942dffe62a0bf5dd871/libusb/libusb/core.c#L60
There are instructions to build libusb for Android here: https://github.com/paritytech/libusb-sys/blob/4418e92c82509d1f049f7942dffe62a0bf5dd871/libusb/android/README
However you are supposed to use
ndk-build
to do that, and we don't necessarily want to rewrite this tool in Rust.Right now on Android we are building libusb manually, but in order to do so we apply a patch on the source code, which is extremely hacky.
Libusb on Android seems to have quite a few runtime issues as well.
A final solution is to remove the dependency on libusb on Android. This is probably the most simple solution, and the one I would suggest. Nobody uses our Android build yet, so we won't break anything.
I'm opening this issue to gather opinion. Any comment on this?
cc #9893 @TriplEight
The text was updated successfully, but these errors were encountered: