mozilla / mozilla/rust-android-gradle
Empty rustJniLibs/ folder when CARGO_TARGET_DIR is defined
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1.3k
- Forks
- 95
- Avg merge
- 15m
- Merged PRs (30d)
- 2
Description
Version 0.9.3
I've try to change CARGO_TARGET_DIR per target like so:
cargo {
...
exec { spec, toolchain ->
spec.environment("CARGO_TARGET_DIR", rustOutputFolder(toolchain.platform))
}
}
As the result, even if, the build folder build/rustJniLibs/.. is created and rust build succeed,
the folder stay empty !
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the cargo exec CARGO_TARGET_DIR setting affects the build/rustJniLibs output path and where built libraries are collected. Reproduce the successful Rust build with a target-specific directory, then verify that rustJniLibs is populated for the target.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100