cargo-apk: Reimplement NDK r23 -lgcc
workaround using RUSTFLAGS
#270
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #265, CC @Mercesa
Any flags passed directly to
cargo rustc
will only be passed to the final compiler invocation. Howevercdylib
library targets in transitive (dependency) crates will still be built (despite not being used in the final binary, that's whatrlib
s are for), but our NDK r23 workaround flags will not reach these compiler invocations rendering b912a6b ("cargo-apk: Work around missing libgcc on NDK r23 with linker script (#189)") ineffective.The same page that documents this discrepancy suggests to resort to
RUSTFLAGS
if arguments are intended for all compiler invocations, which is our intended use-case and unblocks builds with transitivecdylib
dependencies such ashyper
in #265.