rust-android-build

Configure and verify Android Rust builds for RIPDPI across all ABIs.

58|4|Updated Mar 8, 2026

Search Tags:#verification #build #rust #android #abi #ndk

Ready to run

npx skills add https://github.com/po4yka/RIPDPI --skill rust-android-build

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rust-android-build
Source: https://github.com/po4yka/RIPDPI/tree/main/.claude/skills/rust-android-build
Command: npx skills add https://github.com/po4yka/RIPDPI --skill rust-android-build

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Android-specific Rust build, verification, and packaging workflows for RIPDPI, ensuring consistent cross-target results and reproducible releases across ABIs.

Core Features & Use Cases

Per-target 16 KiB alignment guidance and verification for Rust-Android builds.
ABI-specific Rustflags, build profiles, and verification steps integrated with Gradle and cargo.
Auditing and packaging steps to ensure reproducible libripdpi.so outputs before release, including NDK 29 specifics.
Use Case: When modifying native/rust/.cargo/config.toml or workspace profiles, this Skill provides the standardized build flow and checks.

Quick Start

Configure and verify Rust builds for all Android targets using cargo and the Gradle plugin, ensuring 16 KiB alignment and ABI-specific flags.

Frequently Asked Questions about rust-android-build

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I configure Rust Android builds for 16 KiB alignment across all ABIs?▼

Configuring Rust Android builds for 16 KiB alignment involves applying per-target alignment rules and ABI-specific Rustflags using cargo and Gradle integration. This validates artifacts and ensures reproducible outputs across all ABIs before release.

What is the process for verifying Rust native libraries before an Android release?▼

Verifying Rust native libraries before an Android release requires applying per-target alignment rules, checking symbol budgets, and validating artifacts. This ensures consistent cross-target results and reproducible outputs across all ABIs.

Does this Android Rust build workflow support NDK 29 specifics and Gradle integration?▼

Yes, the Android Rust build workflow supports NDK 29 specifics and Gradle plugin integration. It uses cargo tooling with per-ABI targets to apply alignment rules and symbol budgets, keeping the build workflow repeatable and auditable.

How do I standardize cargo build profiles for multiple Android ABIs?▼

Standardizing cargo build profiles for multiple Android ABIs requires modifying native/rust/.cargo/config.toml or workspace profiles. The process applies ABI-specific Rustflags and verification steps to ensure reproducible native library outputs before release.

Why does my Rust Android build fail per-target alignment checks before release?▼

Rust Android builds fail per-target alignment checks when ABI-specific Rustflags and 16 KiB alignment rules are not properly applied. Validating artifacts and auditing packaging steps ensures reproducible native library outputs and resolves cross-target inconsistencies.