The Linux Manuals (man pages) document is an important part of Linux documents. Linux Manuals are organized as several sections. Each section has a group of commands for a specific area in Linux usage, administration or development.
cargo-rustc – Compile a package and all of its dependencies Synopsiscargo rustc [OPTIONS] [–] [<OPTS>…] DescriptionThe specified target for the current package (or package specified by SPEC if provided) will be compiled along with all of its dependencies. The specified … will all be passed to the final compiler invocation, not any of the dependencies….
cargo-run – Run the current project Synopsiscargo run [OPTIONS] [–] [<ARGS>…] DescriptionRun the main binary of the local package (src/main.rs). If neither –bin nor –example are given, then if the project only has one bin target it will be run. Otherwise –bin specifies the bin target to run, and –example specifies the example target to…
cargo-publish – Upload a package to the registry. Synopsiscargo publish [OPTIONS] DescriptionUpload a package to the registry. Options-h, –help Print this message. –host HOST Host to upload the package to. –token TOKEN Token to use when uploading. –no-verify Don’t verify package tarball before publish. –manifest-path PATH Path to the manifest of the package to publish….
cargo-pkgid – Print a fully qualified package specification Synopsiscargo pkgid [OPTIONS] [<SPEC>] DescriptionGiven a <SPEC> argument, print out the fully qualified package id specifier. This command will generate an error if <SPEC> is ambiguous as to which package it refers to in the dependency graph. If no <SPEC> is given, then the pkgid for the…
cargo-package – Create a distributable tarball Synopsiscargo package [OPTIONS] DescriptionAssemble the local package into a distributable tarball. Options-h, –help Print this message. -l, –list Print files included in a package without making one. –no-verify Don’t verify the contents by building them. –no-metadata Ignore warnings about a lack of human-usable metadata. –manifest-path PATH Path to the…
cargo-owner – Manage the owners of a crate of the registry Synopsiscargo owner [OPTIONS] [<CRATE>] DescriptionThis command will modify the owners for a package on the specified registry (or default). Note that owners of a package can upload new versions, and yank old versions. Explicitly named owners can also modify the set of owners, so…
cargo-new – Create a new cargo package Synopsiscargo new [OPTIONS] <PATH> DescriptionCreate a new cargo package at <PATH>. Use the –vcs option to control the version control system to use. Options-h, –help Print this message. –vcs VCS Initialize a new repository for the given version control system (git or hg) or do not initialize any…
cargo-metadata – Machine-readable metadata about the current project Synopsiscargo metadata [OPTIONS] DescriptionOutput the resolved dependencies of a project, the concrete used versions including overrides, in machine-readable format. Options-h, –help Print this message. –features FEATURES Space-separated list of features. –all-features Build all available features. –no-default-features Do not include the default feature. –no-deps Output information only about…
cargo-login – Save an API token from the registry locally Synopsiscargo login [OPTIONS] [<TOKEN>] Options-h, –help Print this message. –host HOST Host to set the token for -v, –verbose Use verbose output. -q, –quiet No output printed to stdout. –color WHEN Coloring: auto, always, never. See Alsocargo(1), cargo-publish(1) CopyrightThis work is dual-licensed under Apache 2.0…
cargo-install – Install a Rust binary Synopsiscargo install [OPTIONS] <CRATE> cargo install [OPTIONS] –list DescriptionInstall a Rust binary This command manages Cargo’s local set of install binary crates. Only packages which have [[bin]] targets can be installed, and all binaries are installed into the installation root’s bin folder. The installation root is determined, in order…
cargo-init – Create a new cargo package in the current directory Synopsiscargo init [OPTIONS] DescriptionCreate a new cargo package in the current directory. Use the –vcs option to control the version control system to use. Options-h, –help Print this message. –vcs VCS Initialize a new repository for the given version control system (git or hg)…
cargo-generate-lockfile – Generate the lockfile for a project Synopsiscargo generate-lockfile [OPTIONS] Options-h, –help Print this message. –manifest-path PATH Path to the manifest to generate a lockfile for. -v, –verbose Use verbose output. -q, –quiet No output printed to stdout. –color WHEN Coloring: auto, always, never. See Alsocargo(1) CopyrightThis work is dual-licensed under Apache 2.0 and…
cargo-fetch – Fetch dependencies of a package from the network Synopsiscargo fetch [OPTIONS] DescriptionIf a lockfile is available, this command will ensure that all of the git dependencies and/or registries dependencies are downloaded and locally available. The network is never touched after a `cargo fetch` unless the lockfile changes. If the lockfile is not available,…
cargo-doc – Build a package’s documentation Synopsiscargo doc [OPTIONS] DescriptionBuild a package’s documentation. By default the documentation for the local package and all dependencies is built. The output is all placed in ‘target/doc’ in rustdoc’s usual format. If the –package argument is given, then SPEC is a package id specification which indicates which package should…
cargo-clean – Remove generated artifacts Synopsiscargo clean [OPTIONS] DescriptionRemove artifacts that cargo has generated in the past. If the –package argument is given, then SPEC is a package id specification which indicates which package should be built. If it is not given, then the current package is built. For more information on SPEC and its…
cargo-check – Check the current project Synopsiscargo check [OPTIONS] DescriptionCheck a local package and all of its dependencies. If the –package argument is given, then SPEC is a package id specification which indicates which package should be checked. If it is not given, then the current package is checked. For more information on SPEC and…
cargo-build – Compile the current project Synopsiscargo build [OPTIONS] DescriptionCompile a local package and all of its dependencies. If the –package argument is given, then SPEC is a package id specification which indicates which package should be built. If it is not given, then the current package is built. For more information on SPEC and…
cargo-bench – Execute benchmarks of a package Synopsiscargo bench [OPTIONS] [–] [<ARGS>…] DescriptionExecute all benchmarks of a local package. All of the trailing arguments are passed to the benchmark binaries generated for filtering benchmarks and generally providing options configuring how they run. If the –package argument is given, then SPEC is a package id specification…
cardos-tool – displays information about Card OS-based security tokens or format them Synopsiscardos-tool [OPTIONS] DescriptionThe cardos-tool utility is used to display information about smart cards and similar security tokens based on Siemens Card/OS M4. Options–info, -i Display information about the card or token. –format, -f Format the card or token. –reader number, -r number Specify…
card_eventmgr – PCSC-Lite Event Manager Syntaxcard_eventmgr [debug] [[no]daemon] [timeout=<msecs>] [config_file=<filename>] [kill] [pidfile=<pidfile>] Descriptioncard_eventmgr is a smart card monitoring tool that listen to the status of the card reader and dispatch actions on several events. card_eventmgr can be used for several actions: like screen lock on card removal. Three events are supported: card insertion, card removal…