CI/android: Select wgpu example by package name instead of manifest path #945
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Specifying a manifest path still allows `cargo` and `cargo-apk` to find the workspace a package belongs to. We've decided that properly implementing [package selection](https://doc.rust-lang.org/cargo/commands/cargo-build.html#package-selection) between `cargo-apk` and `cargo-subcommand` would be [nontrivial](https://github.com/dvc94ch/cargo-subcommand/pull/23/files#diff-23af5356f6001cd3993cd3c801fb7716ea02d1e504081b9fb569332db6107e80R53-R57) and ended up requiring the package to be selected explicitly via `-p` for now.
oisyn
approved these changes
Nov 24, 2022
eddyb
approved these changes
Nov 24, 2022
|
Fwiw I've started reimplementing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Specifying a manifest path still allows
cargoandcargo-apkto find the workspace a package belongs to. We've decided that properly implementing package selection betweencargo-apkandcargo-subcommandwould be nontrivial and ended up requiring the package to be selected explicitly via-pfor now.