CARGO_NDK_OUTPUT_PATH is not absolutized

Question

CARGO_NDK_OUTPUT_PATH is not absolutized

Closed this issue a month ago · 3 comments

If I call cargo ndk at the workspace root with a relative --output-dir, a crate build script not also on the root will resolve an incorrect path. I think cargo build changes the working dir to the manifest dir.

cargo ndk --manifest-path "crates/foo/Cargo.toml" --output-dir "target/build-ndk build

Answer 1 · 2024-08-16T21:45:54.000Z

pull request your way to great success!

Answer 2 · 2024-08-16T21:48:09.000Z

Ok. I will work on this and the panic issue this weekend.

Answer 3 · 2024-08-16T21:48:59.000Z

Looking forward to reviewing your PR :D