-
Notifications
You must be signed in to change notification settings - Fork 386
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
cross --list lists commands that will not run #715
Comments
There seems to be 2 issues here, I believe. This seems to be an issue with The other issue is that An extra feature worth considering is due to custom images, it might be worth writing a config file with extra subcommands that are written at the end of the build step, so that these subcommands are run using cross and the rest fall back to cargo. We could also just parse the output of |
`cross --list` should list the subcommands present for cargo in the image, rather on the host. This works because any option provided before a subcommand has priority over the subcommand. For example, `cargo build --help` prints the help menu for `cargo build`, but `cargo --help build` ignores `build` and prints the help for `cargo`. Therefore, the options `--help`, `--version`, and `--list` can be treated as pseudo-subcommands. Fixes cross-rs#715.
`cross --list` should list the subcommands present for cargo in the image, rather on the host. This works because any option provided before a subcommand has priority over the subcommand. For example, `cargo build --help` prints the help menu for `cargo build`, but `cargo --help build` ignores `build` and prints the help for `cargo`. Therefore, the options `--help`, `--version`, and `--list` can be treated as pseudo-subcommands. Fixes cross-rs#715.
`cross --list` should list the subcommands present for cargo in the image, rather on the host. This works because any option provided before a subcommand has priority over the subcommand. For example, `cargo build --help` prints the help menu for `cargo build`, but `cargo --help build` ignores `build` and prints the help for `cargo`. Therefore, the options `--help`, `--version`, and `--list` can be treated as pseudo-subcommands. This works by capturing the output subcommand list, and then classifying them as either subcommands from the host or container. This also future proofs our logic, if we ever get support for custom subcommands, since only `Other` (unrecognized) subcommands are treated as host commands. Sample Output: ``` Cross Commands: b alias: build bench Execute all benchmarks of a local package Host Commands: afl asm clean Remove artifacts that cargo has generated in the past ``` Fixes cross-rs#715.
`cross --list` should list the subcommands present for cargo in the image, rather on the host. This works because any option provided before a subcommand has priority over the subcommand. For example, `cargo build --help` prints the help menu for `cargo build`, but `cargo --help build` ignores `build` and prints the help for `cargo`. Therefore, the options `--help`, `--version`, and `--list` can be treated as pseudo-subcommands. This works by capturing the output subcommand list, and then classifying them as either subcommands from the host or container. This also future proofs our logic, if we ever get support for custom subcommands, since only `Other` (unrecognized) subcommands are treated as host commands. Sample Output: ``` Cross Commands: b alias: build bench Execute all benchmarks of a local package Host Commands: afl asm clean Remove artifacts that cargo has generated in the past ``` Fixes cross-rs#715.
`cross --list` should list the subcommands present for cargo in the image, rather on the host. This works because any option provided before a subcommand has priority over the subcommand. For example, `cargo build --help` prints the help menu for `cargo build`, but `cargo --help build` ignores `build` and prints the help for `cargo`. Therefore, the options `--help`, `--version`, and `--list` can be treated as pseudo-subcommands. This works by capturing the output subcommand list, and then classifying them as either subcommands from the host or container. This also future proofs our logic, if we ever get support for custom subcommands, since only `Other` (unrecognized) subcommands are treated as host commands. Sample Output: ``` Cross Commands: b alias: build bench Execute all benchmarks of a local package Host Commands: afl asm clean Remove artifacts that cargo has generated in the past ``` Fixes cross-rs#715.
`cross --list` should list the subcommands present for cargo in the image, rather on the host. This works because any option provided before a subcommand has priority over the subcommand. For example, `cargo build --help` prints the help menu for `cargo build`, but `cargo --help build` ignores `build` and prints the help for `cargo`. Therefore, the options `--help`, `--version`, and `--list` can be treated as pseudo-subcommands. This works by capturing the output subcommand list, and then classifying them as either subcommands from the host or container. This also future proofs our logic, if we ever get support for custom subcommands, since only `Other` (unrecognized) subcommands are treated as host commands. Sample Output: ``` Cross Commands: b alias: build bench Execute all benchmarks of a local package Host Commands: afl asm clean Remove artifacts that cargo has generated in the past ``` Co-authored-by: Emil Gardström <emil.gardstrom@gmail.com> Fixes cross-rs#715.
719: Add --list to known subcommands. r=Alexhuszagh a=Alexhuszagh `cross --list` should list the subcommands present for cargo in the image, rather on the host. This works because any option provided before a subcommand has priority over the subcommand. For example, `cargo build --help` prints the help menu for `cargo build`, but `cargo --help build` ignores `build` and prints the help for `cargo`. Therefore, the options `--help`, `--version`, and `--list` can be treated as pseudo-subcommands. Fixes #715. Co-authored-by: Alex Huszagh <ahuszagh@gmail.com>
719: Add --list to known subcommands. r=Alexhuszagh a=Alexhuszagh `cross --list` should list the subcommands present for cargo in the image, rather on the host. This works because any option provided before a subcommand has priority over the subcommand. For example, `cargo build --help` prints the help menu for `cargo build`, but `cargo --help build` ignores `build` and prints the help for `cargo`. Therefore, the options `--help`, `--version`, and `--list` can be treated as pseudo-subcommands. Fixes #715. Co-authored-by: Alex Huszagh <ahuszagh@gmail.com>
"deb" here is cargo-deb. It would be nice if it could be used to generate deb packages for old distros, but since it can't, it shouldn't be listed.
The text was updated successfully, but these errors were encountered: