The official Android build plugin for Infernux. It adds APK/AAB export for ARM64 devices and x64 emulators, with precompiled Vulkan Players and the Android host files required by an Infernux game.
简体中文 · Infernux Engine · Plugin Template · Releases
android-arm64for physical devices andandroid-x64-emulatorfor emulators- Precompiled native Players, CPython 3.13 runtimes, and SDL Java host sources
- Vulkan rendering, Gradle project generation, APK development builds, and AAB release builds
- Android API 26 as the minimum application level
| Package | Version | Compatible engine | Build hosts | Targets |
|---|---|---|---|---|
infernux/platform-android |
0.2.12 | Infernux >=0.4.3; payload 0.4.3 | Windows/Linux x64 | Android ARM64/x64 |
First install Android Support from Infernux Hub → Installs. The Hub-managed support kit contains the large shared JDK, Gradle, Android SDK/NDK, and Android CPython payloads; it is downloaded from the Infernux distribution service and reused by every project.
Then open Plugins in the Editor, select Infernux Android Platform from the official catalog, and import it. The Import button remains unavailable until Hub Android Support is ready. Plugin downloads use the Infernux distribution service first and GitHub Releases as the network fallback.
Choose android-arm64 for a physical device or android-x64-emulator for an emulator. Development builds produce APK files and release builds produce AAB files by default. A release AAB remains unsigned until you configure INFERNUX_ANDROID_KEYSTORE, INFERNUX_ANDROID_KEY_ALIAS, and the corresponding password variables.
Ordinary users do not run CMake or download SDK components during import/export. The Player requires Vulkan; there is no OpenGL ES rendering path.
The installable platform plugin lives in package/; the much larger shared Android Support kit is deliberately not duplicated here. Native sources, release scripts, tests, and CI remain outside the package. Maintainer builds publish both ABI payloads directly into package/, and a matching v<version> tag releases the .inxpkg and manifest through GitHub Actions.
MIT. Bundled third-party components and Android tooling retain their own licenses.