3 ms·

Could this be used to relocate Android-native libraries to other platforms? Even if the architecture matches, the bionic libc calls is what I found more challen

• jeroenhd 5y ago
  The tool moves runs the application and all of its dependencies in a container for compatibility, but on Android with bionic that would probably imply moving all of libc with the app. I don't think that'll go down as easily, as the entire bionic framework is integrated quite deeply with the rest of the system. For "simple" bionic libc calls, an LD_PRELOAD shim might be enough for many binaries, though. You'd need to translate all the bionic libc calls to your system's libc calls, but that might just be easier than it seems because the level of compatibility between the two. Bionic is actually a subset of POSIX libc, so you should be able to map all calls to your normal system calls. I don't know how well-maintained the project is, but https://github.com/Cloudef/android2gnulinux https://github.com/Cloudef/android2gnulinux might just do the trick for you.
  • captn3m0 5y ago
    I've tried using https://github.com/libhybris/libhybris https://github.com/libhybris/libhybris directly earlier. Will try this.