Help specifying toolchain
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- build-system, mobile
Research direction
Start by comparing the failing linker-wrapper.bat command with the working Android NDK clang.cmd command shown in the report. Inspect how local.properties supplies the NDK toolchain location and determine the directory format needed for the linker configuration. Done means the default build uses the intended NDK linker and exits successfully on the reported Windows setup.
Written by the indexing model from the issue text.
Description
By default, the build runs the following command:
rustc --crate-name lusna_ffi --edition=2018 lusna_ffi\src\lib.rs --error-format=json --json=diagnostic-rendered-ansi --crate-type cdylib --emit=dep-info,link -Cembed-bitcode=no -C debuginfo=2 -C metadata=fcf7fc3e883754d2 --out-dir C:\hyxe_wave\target\x86_64-linux-android\debug\deps --target x86_64-linux-android -C linker=C:\Users\tbrau\AndroidStudioProjects\Lusna\build\linker-wrapper\linker-wrapper.bat -C incremental=C:\hyxe_wave\target\x86_64-linux-android\debug\incremental -L dependency=C:\hyxe_wave\target\x86_64-linux-android\debug\deps -L dependency=C:\hyxe_wave\target\debug\deps --extern libc=C:\hyxe_wave\target\x86_64-linux-android\debug\deps\liblibc-f65a499a1c08d6d0.rlib -Ctarget-feature=+aes,+sse2,+sse4.1,+ssse3
Notice: linker=C:\Users\tbrau\AndroidStudioProjects\Lusna\build\linker-wrapper\linker-wrapper.bat
This fails with a nonzero exit code.
However, when I run the command in the command prompt with:
rustc --crate-name lusna_ffi --edition=2018 lusna_ffi\src\lib.rs --error-format=json --json=diagnostic-rendered-ansi --crate-type cdylib --emit=dep-info,link -Cembed-bitcode=no -C debuginfo=2 -C metadata=fcf7fc3e883754d2 --out-dir C:\hyxe_wave\target\x86_64-linux-android\debug\deps --target x86_64-linux-android -C linker=C:/android-ndk-r21d/toolchains/llvm/prebuilt/windows-x86_64/bin/x86_64-linux-android30-clang.cmd -C incremental=C:\hyxe_wave\target\x86_64-linux-android\debug\incremental -L dependency=C:\hyxe_wave\target\x86_64-linux-android\debug\deps -L dependency=C:\hyxe_wave\target\debug\deps --extern libc=C:\hyxe_wave\target\x86_64-linux-android\debug\deps\liblibc-f65a499a1c08d6d0.rlib -Ctarget-feature=+aes,+sse2,+sse4.1,+ssse3
where linker=C:/android-ndk-r21d/toolchains/llvm/prebuilt/windows-x86_64/bin/x86_64-linux-android30-clang.cmd, it runs perfectly (zero exit code). I see that I can change the local.properties to specify the ndk toolchain location, but which directory should be input therein? Thanks
- 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
- 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.
More from mozilla/rust-android-gradle
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mozilla/rust-android-gradle#174 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
mozilla/rust-android-gradle#166 · 1 comment · 3 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
mozilla/rust-android-gradle#163 · 2 comments · 2 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
mozilla/rust-android-gradle#158 · 7 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
mozilla/rust-android-gradle#152 · 1 comment ·
All issues in mozilla/rust-android-gradle
Similar issues
-
Source is down
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
keiyoushi/extensions-source#19491 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
MTES-MCT/rapportnav2#1557 ·
Maintainers usually reply within 1 day
-
ready-for-agent
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
emm3000/Just-Chill#543 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
vaadin/intellij-plugin#600 ·
-
accessibility
Difficulty 2/5 1-3 hours Newbie friendliness 65/100