cargo-ndk icon indicating copy to clipboard operation
cargo-ndk copied to clipboard

.cargo/config.toml not being read

Open baxterjo opened this issue 1 month ago • 0 comments

I am trying to get some of my project level environment vars set up in a .cargo/config.toml and I am not seeing it being loaded correctly when using cargo ndk.

my config

[target.aarch64-linux-android]
runner = "cargo ndk-runner"

[target.aarch64-linux-android.env]
CARGO_NDK_PLATFORM = "24"

If I run cargo config I can see that my configs are being picked up:

❯ cargo +nightly -Z unstable-options config get | grep android
target.aarch64-linux-android.env.CARGO_NDK_PLATFORM = "24"
target.aarch64-linux-android.runner = "cargo ndk-runner"

But when I run cargo ndk-env:

❯ cargo ndk-env --target aarch64-linux-android | grep "FLAGS"
export CFLAGS_aarch64_linux_android="--target=aarch64-linux-android21"
export CXXFLAGS_aarch64_linux_android="--target=aarch64-linux-android21"

Then with platform given as a command line arg:

❯ cargo ndk-env --target aarch64-linux-android --platform 24 | grep "FLAGS"
export CFLAGS_aarch64_linux_android="--target=aarch64-linux-android24"
export CXXFLAGS_aarch64_linux_android="--target=aarch64-linux-android24"

It seems like cargo run is also not picking up the ndk-runner setting and I have to invoke ndk-runner manually. Which now that I'm typing this out might mean its a cargo issue?

baxterjo avatar Dec 05 '25 01:12 baxterjo