Menu
Android Rust builds, cross-compilation targets, and Gradle jniLibs integration.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use this skill to generate well-branded interfaces and assets for RIPDPI (an Android-native, Compose-first VPN and DPI-bypass app), either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, brand-ship icons, and an interactive UI kit of every public composable from the live ui/components tree.
Use when managing the Rust workspace, adding/removing crates, editing workspace dependencies, running cargo nextest/audit/deny, configuring Cargo profiles for Android cross-compilation, debugging Cargo.lock churn, migrating crate edition, or wiring Gradle to cargo via the ripdpi.android.rust-native plugin.
Use when modifying the diagnostics scan pipeline, ScanRequest/ScanReport types, ProbeTask families, ripdpi-monitor-engine / ripdpi-diagnostics-* crates, strategy-probe candidates, the diagnostics catalog (packs/profiles), wire-schema contracts between Rust and Kotlin, DIAGNOSTICS_ENGINE_SCHEMA_VERSION, golden contract tests, or adding a new probe type / profile. Triggers on diagnostics scans, strategy probes, automatic audit, dpi-detector profiles, or anything in core/diagnostics or native/rust/crates/ripdpi-monitor-*.
Android-specific Rust build, verification, and packaging — per-target 16 KiB page alignment, size-optimized release profile, ELF symbol allowlist, .so size budgets, NDK 29 specifics. Use when modifying .cargo/config.toml for Android targets, the workspace [profile.release] / [profile.android-jni] block, or when verifying a built .so before release.
Telemetry and observability discipline for the RIPDPI Android Rust stack — control-plane vs data-plane logging, bounded flume event queues, atomic counters, snapshot polling, readiness callbacks, and deterministic JSON contracts. Use when authoring or modifying telemetry emission code, the bounded event ring, the Kotlin-side telemetry consumer, or any per-packet logging.
Custom detekt rules, DI/privacy/suppression guardrails, detekt.yml configuration, and false-positive triage.
| name | rust-android-ndk |
| description | Android Rust builds, cross-compilation targets, and Gradle jniLibs integration. |
RIPDPI builds Rust libraries as Android .so files with plain cargo build --locked plus the Android NDK linker toolchain. The project-standard entrypoint is :core:engine:buildRustNativeLibs, which is registered by the ripdpi.android.rust-native convention plugin and builds the native/rust workspace before preBuild.
# Install Rust Android targets
rustup target add \
aarch64-linux-android \
armv7-linux-androideabi \
x86_64-linux-android \
i686-linux-android
Set sdk.dir in local.properties or ANDROID_SDK_ROOT, and make sure the matching NDK exists at $ANDROID_SDK_ROOT/ndk/29.0.14206865.
| Android ABI | Rust target | Min API |
|---|---|---|
arm64-v8a | aarch64-linux-android | 27 |
armeabi-v7a | armv7-linux-androideabi | 27 |
x86_64 | x86_64-linux-android | 27 |
x86 | i686-linux-android | 27 |
RIPDPI supports all four ABIs with minSdk 27.
./gradlew :core:engine:buildRustNativeLibs
This creates generated/jniLibs/<abi>/libripdpi.so and generated/jniLibs/<abi>/libripdpi-tunnel.so.
libripdpi.so includes both the proxy runtime bridge and the diagnostics monitor path (ripdpi-monitor-engine through the Android diagnostics adapter). Native diagnostics changes use the same Android build path as proxy changes.
The task sets the target linker for each ABI explicitly and builds:
native/rust package ripdpi-androidnative/rust package ripdpi-tunnel-androidThe ABI set comes from gradle.properties. Local non-release builds default to ripdpi.localNativeAbisDefault=arm64-v8a, and ripdpi.localNativeAbis=x86_64 is the fast path for emulator-heavy iteration. CI and release builds must keep the full ABI set.
[lib]
crate-type = ["cdylib"] # Required: produces .so for Android
[dependencies]
jni = "0.22" # JNI bindings
log = "0.4" # Logging
android-support = { workspace = true } # Android logging + JNI support helpers
[profile.android-jni]
inherits = "release"
opt-level = "z" # Optimize for size
panic = "unwind"
[profile.android-jni-dev]
inherits = "dev"
opt-level = 1 # Faster local iteration with symbols
panic = "unwind"
crate-type = ["cdylib"] is mandatory because Android loads the libraries through System.loadLibrary(). RIPDPI's Gradle task selects the Cargo profile from gradle.properties: release-like builds use ripdpi.nativeCargoProfile, while local non-release builds can fall back to ripdpi.localNativeCargoProfileDefault.
Android 15+ requires 16KB page alignment. Add to .cargo/config.toml:
[target.aarch64-linux-android]
rustflags = ["-C", "link-arg=-Wl,-z,max-page-size=16384"]
[target.armv7-linux-androideabi]
rustflags = ["-C", "link-arg=-Wl,-z,max-page-size=16384"]
[target.x86_64-linux-android]
rustflags = ["-C", "link-arg=-Wl,-z,max-page-size=16384"]
[target.i686-linux-android]
rustflags = ["-C", "link-arg=-Wl,-z,max-page-size=16384"]
| Mistake | Fix |
|---|---|
Missing crate-type = ["cdylib"] | Required for .so output; rlib is Rust-only |
| Forgetting 16KB page alignment | Add -Wl,-z,max-page-size=16384 rustflag per target |
| Not pointing Gradle at the Android SDK/NDK | Set sdk.dir or ANDROID_SDK_ROOT and install the configured NDK |
| Hardcoding a Cargo profile in local commands | Prefer :core:engine:buildRustNativeLibs; the convention plugin already selects android-jni or android-jni-dev based on build context |
| Forgetting to keep Android profiles unwind-safe | android-jni and android-jni-dev must keep panic = "unwind" so JNI boundaries can translate failures safely |
| Wrong target triple | Use armv7-linux-androideabi (not armv7a-) for armeabi-v7a |
rust-code-style -- Rust code style rules for the native workspacerust-lint-config -- Clippy, rustfmt, and cargo-deny configurationrust-crate-architecture -- Crate layering and dependency rulesnative-jni-development -- JNI boundary rules and diagnostics payload compatibility