Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cargo-apk: Append --target to blanket cargo apk -- calls when not provided #287

Merged
merged 1 commit into from
Jun 10, 2022

Conversation

MarijnS95
Copy link
Member

@MarijnS95 MarijnS95 commented Jun 10, 2022

Depends on #286, #283

When the user doesn't provide a --target we default the triple to the currently connected device over adb, or otherwise fall back to aarch64.

While this triple is always used to determine what NDK environment to provide, it's never added to the arguments passed after --; for example a cargo apk -- test --no-run will try to build tests for the host unless explicitly called with --target.


I can't currently think of any command that one might want to run under cargo apk -- with an NDK environment, but without support for --target. If there is, that's a valid argument to not pass this flag (but perhaps clearly document it, maybe even warn about it if we don't find --target in the call?).

@MarijnS95
Copy link
Member Author

@msiglreith Thoughts? If we want this, we should probably get it in right in the next patch release (that I'd like to do soon™ to fix the winit CI with #286), and see how it fares.

Or is there a command you think may not support --target but may be relevant to run here?

… provided

When the user doesn't provide a `--target` we default the triple to the
currently connected device over `adb`, or otherwise fall back to
`aarch64`.

While this triple is always used to determine what NDK environment to
provide, it's never added to the arguments passed after `--`; for
example a `cargo apk -- test --no-run` will try to build tests for the
host unless explicitly called with `--target`.
Copy link
Contributor

@msiglreith msiglreith left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fine for me
check, build, test, clippy, doc and bench seem all to support it which are probably the most used CI configurations and which might user want through cargo-apk

@MarijnS95
Copy link
Member Author

Let's go for it then, this is probably a net-improvement and otherwise we'll come up with an alternative 👍

@MarijnS95 MarijnS95 merged commit 3e2175f into master Jun 10, 2022
@MarijnS95 MarijnS95 deleted the cargo-apk-target branch June 10, 2022 19:44
@MarijnS95 MarijnS95 added the type: bug Dang, that shouldn't have happened label Jun 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Dang, that shouldn't have happened
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants