Jan 15, 2025 23:10:51 [email protected]: > Hi Muflone, > >> For examples, please refer to the packages listed in "Required by" section: >> https://aur.archlinux.org/packages/android-configure?all_reqs=1#pkgreqs > > e.g. > > android-aarch64-a52dec (make) > android-aarch64-alsa-lib (make) > android-aarch64-cdparanoia (make) > android-aarch64-cppunit (make) > android-aarch64-curl (make) > android-aarch64-faac (make) > android-aarch64-ffmpeg (make) > ... > ... > >> Many android packages are runtime for the Android emulator run in Arch >> Linux, not for Android. They are the systems the emulator will run. > > Are there any Android emulator packages which require android-$arch-$package > as build / runtime dependencies in their PKGBUILD? > When I checked `android-emulator`, [1] it does not list any > android-$arch-$package. > > gnlrdrvo > > [1] https://aur.archlinux.org/packages/android-emulator
Not muflone but from a quick look at the android-configure package which is a build dependency for all of them and the 2 dependencies of android-configure, it appears to me that these packages are intended for cross-compilation towards android rather than emulating. Besides, the purpose of emulating isn't to add packages to the host but rather to run them in the emulator, so regular android apk's would suffice for that. Cross-compiling however does require you to have the dependencies of a different operating system and/or architecture for which you are cross-compiling installed. Kusoneko
