Searched refs:cargo (Results 1 – 25 of 372) sorted by relevance
12345678910>>...15
8 cargo clippy --all -- -D warnings10 cargo clean11 cargo doc --features "$FEATURES" --all --no-deps16 travis-cargo doc-upload || true18 cargo fmt --all -- --check21 cargo build -Z minimal-versions25 cargo build --features "$FEATURES" $BUILD_ARGS27 cargo test --features "$FEATURES" --all28 cargo test --features "$FEATURES" --benches32 cargo test --benches[all …]
8 cargo install cargo-hack13 cargo hack "${cmd}" --each-feature --optional-deps15 cargo "${cmd}" --all-features17 cargo doc --no-deps --all-features21 cargo check --benches24 cargo clean25 cargo update -Zminimal-versions26 cargo check --all-features
7 cargo clean17 cargo miri setup19 cargo miri test --verbose20 cargo miri test --verbose --features union21 cargo miri test --verbose --all-features
11 ### Use `cargo fuzz`!13 [The recommended way to use this crate with `cargo fuzz`!][cargo-fuzz].15 [cargo-fuzz]: https://github.com/rust-fuzz/cargo-fuzz21 First create a new cargo project:24 $ cargo new --bin fuzzed51 $ cargo rustc -- \
6 cargo check --target $TARGET --no-default-features8 cargo test --features x128 --target $TARGET9 cargo test --features x128 --target $TARGET --release11 cargo build --target $TARGET --no-default-features12 cargo build --target $TARGET
8 cargo test11 cargo test --doc25 cargo test --test default --no-default-features --features "$f"27 cargo test --test default-bytes --no-default-features --features "$f"
15 cargo test --test {{TEST}}18 cargo test --test {{TEST}} --features debug21 cargo test --features "yaml unstable"24 cargo bench && just remove-nightly33 cargo build --features lints && just remove-nightly36 cargo clean
26 crate_src_abspath=`cargo metadata --no-deps --format-version 1 | jq -r '.workspace_root'`42 cargo build --bins44 cd `cargo metadata --format-version 1 --no-deps | jq -r '.target_directory'`51 /rust/bin/cargo "$@"
9 cargo build13 rustup run nightly cargo build --features=clippy16 cargo doc21 cargo test
15 --env CARGO_HOME=/cargo \16 --volume $HOME/.cargo:/cargo \19 cargo run --manifest-path systest/Cargo.toml -vv
29 cargo test --all32 cargo fmt --all -- --check35 cargo clippy --all-targets --all-features -- -D warnings38 cargo clean41 cargo build --lib44 cargo build --manifest-path=echo_server/Cargo.toml
19 cargo update22 env LIBSQLITE3_SYS_BUNDLING=1 cargo build --features "buildtime_bindgen" --no-default-features26 cargo update27 cargo test --features "backup blob chrono functions limits load_extension serde_json trace vtab bun…
28 cargo test --doc29 cargo build --release --examples44 …e only guide line is we need to make sure `cargo fmt` doesn't change anything. So it's recommended…76 cargo test --all-features82 cargo test --no-default-features --lib95 cargo install wasm-bindgen-cli103 cargo test --lib --target wasm32-unknown-unknown115 …r the code coverage information you may want to use [cargo-tarpaulin](https://crates.io/crates/car…120 cargo install cargo-tarpaulin127 cargo tarpaulin --all-features --run-types Tests Doctests -o Xml --output-dir target/test
23 cargo fmt40 cargo +${MSRV} build42 cargo publish
22 ## cargo-fuzz support24 Rust integration with OSS-Fuzz is expected to use [`cargo25 fuzz`](https://github.com/rust-fuzz/cargo-fuzz) to build fuzzers. The `cargo27 correct libFuzzer on OSS-Fuzz itself. Note that using `cargo fuzz` also makes it32 First you'll want to follow the [setup instructions for `cargo fuzz`65 `cargo fuzz` pre-installed and in `PATH`. In the `Dockerfile` for your project82 cargo fuzz build -O86 Note that you likely want to pass the `-O` flag to `cargo fuzz build` which
25 cargo test $TARGET_FLAG -- --quiet34 cargo run $TARGET_FLAG --bin=alloc_check43 cargo bench $TARGET_FLAG
35 cargo fetch44 cargo run --bin libra-fuzzer list --no-desc > fuzzer_list49 cargo run --bin libra-fuzzer generate -n 128 $line85 …cargo build --manifest-path fuzz/Cargo.toml --bin fuzzer_builder --release --target x86_64-unknown…
11 mkdir -p $HOME/.cargo12 ln -s /usr/local/bin $HOME/.cargo/bin25 cat > /root/.cargo/config <<EOF
55 $ cargo run --manifest-path=tools/apps/Cargo.toml --bin quiche-client -- https://quic.tech:8443/61 $ cargo run --manifest-path=tools/apps/Cargo.toml --bin quiche-server -- \240 When running ``cargo build``, a static library called ``libquiche.a`` will be259 and then built using cargo:262 $ cargo build --examples265 cargo can also be used to run the testsuite:268 $ cargo test273 when building quiche using cargo, but requires the `cmake` command to be283 $ QUICHE_BSSL_PATH="/path/to/boringssl" cargo build --examples314 way using [cargo-ndk]. You need to install [cargo-ndk] first.[all …]
19 -e CARGO_HOME=/cargo \21 -v $(dirname $(dirname `which cargo`)):/cargo \
19 * [ ] `cargo fmt -- --check` passes.20 * [ ] `cargo +nightly clippy` has no warnings.21 * [ ] `cargo test` passes.
21 * [ ] `cargo fmt -- --check` passes.22 * [ ] `cargo +nightly clippy` has no warnings.23 * [ ] `cargo test` passes.
13 let cargo = &*env::var("CARGO").unwrap_or_else(|_| "cargo".into()); in expandtest() localVariable14 if !has_command(&[cargo, "expand"]) || !has_command(&[cargo, "fmt"]) { in expandtest()
10 (cd .. && cargo build $@)11 cargo test $@
7 cargo publish14 cargo publish