Builds and packages Rust static libraries as XCFrameworks for iOS apps.
npx skills add https://github.com/po4yka/rust-skills --skill rust-ios-build-po4yka
Please help me install this Agent Skill. Skill: rust-ios-build Source: https://github.com/po4yka/rust-skills/tree/main/skills/rust-ios-build Command: npx skills add https://github.com/po4yka/rust-skills --skill rust-ios-build-po4yka
aarch64-apple-ios and aarch64-apple-ios-sim staticlibs with one IPHONEOS_DEPLOYMENT_TARGET, then validates platform and minimum OS per object with otool -l and nm -gU. - XCFramework and SwiftPM packaging: Assembles the XCFramework with xcodebuild -create-xcframework, stages headers and modulemaps, and integrates via local or remote SwiftPM binaryTarget with checksum handling. - Release evidence and triage: Covers dSYM UUID matching, simulator and physical-device smoke tests, code signing boundaries, privacy manifest routing, and a symptom-to-fix table for common linker and packaging failures. - Use Case: You maintain a UniFFI-based Rust core for an iOS app. Use this Skill to build both slices, package the XCFramework, wire it into SwiftPM, and run a simulator smoke test that calls your exported ABI version function before every release. ## Quick Start Use the rust-ios-build skill to build my Rust FFI crate for iOS device and simulator, package it as an XCFramework, and verify the slices.High-intent search queries and answers about installing and using this skill.
Build a Rust staticlib for iOS with cargo rustc --target aarch64-apple-ios --crate-type staticlib, and use aarch64-apple-ios-sim for the Apple silicon simulator. Export one IPHONEOS_DEPLOYMENT_TARGET for every cargo invocation so all objects share the same minimum OS.
Package the device and simulator archives with xcodebuild -create-xcframework, passing each library with its headers directory containing the C header and modulemap. Reference it in SwiftPM as a binaryTarget named after the module, using a local path or a remote ZIP with a swift package compute-checksum value.
This warning means IPHONEOS_DEPLOYMENT_TARGET was unset or stale for one object, often a cc-built C object defaulting to the SDK version. Export the variable, rebuild in a fresh CARGO_TARGET_DIR, and re-run the otool -l slice check; treat the warning as a failure.
No, each Rust staticlib carries its own copy of std and the Rust Reference says multiple Rust staticlibs are likely to conflict, producing duplicate symbol errors. Put every Rust crate the app needs behind one FFI crate and build a single staticlib.
No, a staticlib does not carry the system libraries and frameworks its dependencies link. Run cargo rustc with --print=native-static-libs and add each listed -framework and -l flag to the Swift consumer's linker settings.
Compare UUIDs with dwarfdump --uuid on both the app executable inside the .xcarchive and the app dSYM, and require the UUID sets to match. Reject a dSYM from a rebuild even when the Git revision and version are identical.
GlubusCreate safe Rust FFI bindings with #[repr(C)] structs and extern "C exports across multiple targets.
dustinober1Builds, archives, exports, and uploads Xcode apps for App Store Connect submission.
novelsagaExpose Rust types to C/C++ and WASM via Diplomat FFI bindings.
kagura-aiManage long-term project memory sessions via Kagura Memory Cloud.