Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Empty rustJniLibs/ folder when CARGO_TARGET_DIR is defined

Open
#125 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust

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.

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 !

Dominant language
Kotlin
Stars
1.3k
Forks
95
PR merge metrics
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mozilla/rust-android-gradle

All issues in mozilla/rust-android-gradle

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.