Chapter 2. cargo

2.1. Installing cargo
Copier lien

Install Rust Toolset, see Section 1.4, “Installing Rust Toolset”.
Note
cargo is installed as a part of Rust Toolset.
On Red Hat Enterprise Linux 7, cargo is provided by the rust-toolset-1.35-cargo package.
On Red Hat Enterprise Linux 8, cargo is provided by the rust-toolset module.

2.2. Creating a New Project
Copier lien

To create a Rust program on the command line, run the cargo tool as follows:

For Red Hat Enterprise Linux 7:

scl enable rust-toolset-1.35 'cargo new --bin project_name'

$ scl enable rust-toolset-1.35 'cargo new --bin project_name'

Copy to Clipboard

Toggle word wrap

For Red Hat Enterprise Linux 8:
```
cargo new --bin project_name
```
```
$ cargo new --bin project_name
```
Copy to Clipboard Toggle word wrap

This creates a directory project_name containing a text file named Cargo.toml and a subdirectory src containing a text file named main.rs.

To configure the project and add dependencies, edit the file Cargo.toml. See Section 2.7, “Configuring Project Dependencies”.

To edit the project code, edit the file main.rs and add new source files in the src subdirectory as needed.

To create a project for a cargo package instead of a program, run the cargo tool on the command line as follows:

For Red Hat Enterprise Linux 7:

scl enable rust-toolset-1.35 'cargo new --lib project_name'

$ scl enable rust-toolset-1.35 'cargo new --lib project_name'

Copy to Clipboard

Toggle word wrap

For Red Hat Enterprise Linux 8:
```
cargo new --lib project_name
```
```
$ cargo new --lib project_name
```
Copy to Clipboard Toggle word wrap

Note that you can execute any command using the scl utility on Red Hat Enterprise Linux 7, causing it to be run with the Rust Toolset binaries available. This allows you to run a shell session with Rust Toolset cargo command directly available:

scl enable rust-toolset-1.35 'bash'

$ scl enable rust-toolset-1.35 'bash'

Copy to Clipboard

Toggle word wrap

Example 2.1. Creating a Project using cargo

Create a new Rust project called helloworld:

For Red Hat Enterprise Linux 7:

scl enable rust-toolset-1.35 'cargo new --bin helloworld'

$ scl enable rust-toolset-1.35 'cargo new --bin helloworld'
     Created binary (application) helloworld project

Copy to Clipboard

Toggle word wrap

For Red Hat Enterprise Linux 8:

cargo new --bin helloworld

$ cargo new --bin helloworld
     Created binary (application) helloworld project

Copy to Clipboard

Toggle word wrap

Examine the result:

cd helloworld
tree
cat src/main.rs

$ cd helloworld
$ tree
.
├── Cargo.toml
└── src
    └── main.rs

1 directory, 2 files
$ cat src/main.rs
fn main() {
    println!("Hello, world!");
}

Copy to Clipboard

Toggle word wrap

A directory helloworld is created for the project, with a file Cargo.toml for tracking project metadata, and a subdirectory src containing the main source code file main.rs.

The source code file main.rs has been initialized by cargo to a sample hello world program.

Note

The tree tool is available from the default Red Hat Enterprise Linux repositories. To install it:

yum install tree

# yum install tree

Copy to Clipboard

Toggle word wrap

2.3. Building a Project
Copier lien

To build a Rust project on the command line, change to the project directory and run the cargo tool as follows:

For Red Hat Enterprise Linux 7:
```
scl enable rust-toolset-1.35 'cargo build'
```
```
$ scl enable rust-toolset-1.35 'cargo build'
```
Copy to Clipboard Toggle word wrap
For Red Hat Enterprise Linux 8:
```
cargo build
```
```
$ cargo build
```
Copy to Clipboard Toggle word wrap

This resolves all dependencies of the project, downloads the missing dependencies, and compiles the project using the rustc compiler.

By default, the project is built and compiled in debug mode. To build the project in release mode, run the cargo tool with the --release option as follows:

For Red Hat Enterprise Linux 7:

scl enable rust-toolset-1.35 'cargo build --release'

$ scl enable rust-toolset-1.35 'cargo build --release'

Copy to Clipboard

Toggle word wrap

For Red Hat Enterprise Linux 8:
```
cargo build --release
```
```
$ cargo build --release
```
Copy to Clipboard Toggle word wrap

Example 2.2. Building a Project using cargo

This example assumes that you have successfully created the Rust project helloworld according to Example 2.1, “Creating a Project using cargo”.

Change to the directory helloworld and build the project:

For Red Hat Enterprise Linux 7:

scl enable rust-toolset-1.35 'cargo build'

$ scl enable rust-toolset-1.35 'cargo build'
   Compiling helloworld v0.1.0 (file:///home/vslavik/helloworld)
    Finished dev [unoptimized + debuginfo] target(s) in 0.51 secs

Copy to Clipboard

Toggle word wrap

For Red Hat Enterprise Linux 8:

cargo build

$ cargo build
   Compiling helloworld v0.1.0 (file:///home/vslavik/helloworld)
    Finished dev [unoptimized + debuginfo] target(s) in 0.51 secs

Copy to Clipboard

Toggle word wrap

Examine the result:

tree

$ tree
.
├── Cargo.lock
├── Cargo.toml
├── src
│   └── main.rs
└── target
    └── debug
        ├── build
        ├── deps
        │   └── helloworld-b7c6fab39c2d17a7
        ├── examples
        ├── helloworld
        ├── helloworld.d
        ├── incremental
        └── native

8 directories, 6 files

Copy to Clipboard

Toggle word wrap

A subdirectory structure has been created, starting with the directory target. Since the project was built in debug mode, the actual build output is contained in a further subdirectory debug. The actual resulting executable file is target/debug/helloworld.

Note

The tree tool is available from the default Red Hat Enterprise Linux repositories. To install it:

yum install tree

# yum install tree

Copy to Clipboard

Toggle word wrap

2.4. Checking a Program
Copier lien

To verify that a Rust program managed by cargo can be built, on the command line change to the project directory and run the cargo tool as follows:

For Red Hat Enterprise Linux 7:
```
scl enable rust-toolset-1.35 'cargo check'
```
```
$ scl enable rust-toolset-1.35 'cargo check'
```
Copy to Clipboard Toggle word wrap
For Red Hat Enterprise Linux 8:
```
cargo check
```
```
$ cargo check
```
Copy to Clipboard Toggle word wrap

Note

Consider using cargo check over cargo build for verification of a Rust program validity when you do not need the executable code. The cargo check command is faster than a full project build using the cargo build command, because it does not generate the executable code.

By default, the project is checked in debug mode. To check the project in release mode, run the cargo tool with the --release option as follows:

For Red Hat Enterprise Linux 7:

scl enable rust-toolset-1.35 'cargo check --release'

$ scl enable rust-toolset-1.35 'cargo check --release'

Copy to Clipboard

Toggle word wrap

For Red Hat Enterprise Linux 8:
```
cargo check --release
```
```
$ cargo check --release
```
Copy to Clipboard Toggle word wrap

Example 2.3. Checking a Program with cargo

This example assumes that you have successfully built the Rust project helloworld according to Example 2.2, “Building a Project using cargo”.

Change to the directory helloworld and check the project:

For Red Hat Enterprise Linux 7:

scl enable rust-toolset-1.35 'cargo check'

$ scl enable rust-toolset-1.35 'cargo check'
   Compiling helloworld v0.1.0 (file:///home/vslavik/helloworld)
    Finished dev [unoptimized + debuginfo] target(s) in 0.5 secs

Copy to Clipboard

Toggle word wrap

For Red Hat Enterprise Linux 8:

cargo check

$ cargo check
   Compiling helloworld v0.1.0 (file:///home/vslavik/helloworld)
    Finished dev [unoptimized + debuginfo] target(s) in 0.5 secs

Copy to Clipboard

Toggle word wrap

The project is checked, with output similar to that of the cargo build command. However, the executable file is not generated. You can verify this by comparing the current time with the time stamp of the executable file:

date
ls -l target/debug/helloworld

$ date
Fri Oct 13 08:53:21 CEST 2017
$ ls -l target/debug/helloworld
-rwxrwxr-x. 2 vslavik vslavik 252624 Oct 13 08:48 target/debug/helloworld

Copy to Clipboard

Toggle word wrap

2.5. Running a Program
Copier lien

To run a Rust program managed as a project by cargo on the command line, change to the project directory and run the cargo tool as follows:

For Red Hat Enterprise Linux 7:
```
scl enable rust-toolset-1.35 'cargo run'
```
```
$ scl enable rust-toolset-1.35 'cargo run'
```
Copy to Clipboard Toggle word wrap
For Red Hat Enterprise Linux 8:
```
cargo run
```
```
$ cargo run
```
Copy to Clipboard Toggle word wrap

If the program has not been built yet, cargo will run a build before running the program.

Note

Consider using cargo to run a Rust program during development. It will correctly resolve the output path independently of the build mode.

By default, the project is built in debug mode. To build the project in release mode before running, run the cargo tool with the --release option as follows:

For Red Hat Enterprise Linux 7:

scl enable rust-toolset-1.35 'cargo run --release'

$ scl enable rust-toolset-1.35 'cargo run --release'

Copy to Clipboard

Toggle word wrap

For Red Hat Enterprise Linux 8:
```
cargo run --release
```
```
$ cargo run --release
```
Copy to Clipboard Toggle word wrap

Example 2.4. Running a Program with cargo

This example assumes that you have successfully built the Rust project helloworld according to Example 2.2, “Building a Project using cargo”.

Change to the directory helloworld and run the project:

For Red Hat Enterprise Linux 7:

scl enable rust-toolset-1.35 'cargo run'

$ scl enable rust-toolset-1.35 'cargo run'
    Finished dev [unoptimized + debuginfo] target(s) in 0.0 secs
     Running target/debug/helloworld
Hello, world!

Copy to Clipboard

Toggle word wrap

For Red Hat Enterprise Linux 8:

cargo run

$ cargo run
    Finished dev [unoptimized + debuginfo] target(s) in 0.0 secs
     Running target/debug/helloworld
Hello, world!

Copy to Clipboard

Toggle word wrap

cargo first rebuilds the project, and then runs the resulting executable file.

In this example, there were no changes to the source code since last build. As a result, cargo did not have to rebuild the executable file, but merely accepted it as current.

2.6. Running Project Tests
Copier lien

To run tests for a cargo project on the command line, change to the project directory and run the cargo tool as follows:

For Red Hat Enterprise Linux 7:
```
scl enable rust-toolset-1.35 'cargo test'
```
```
$ scl enable rust-toolset-1.35 'cargo test'
```
Copy to Clipboard Toggle word wrap
For Red Hat Enterprise Linux 8:
```
cargo test
```
```
$ cargo test
```
Copy to Clipboard Toggle word wrap

By default, the project is tested in debug mode. To test the project in release mode, run the cargo tool with the --release option as follows:

For Red Hat Enterprise Linux 7:

scl enable rust-toolset-1.35 'cargo test --release'

$ scl enable rust-toolset-1.35 'cargo test --release'

Copy to Clipboard

Toggle word wrap

For Red Hat Enterprise Linux 8:
```
cargo test --release
```
```
$ cargo test --release
```
Copy to Clipboard Toggle word wrap

Example 2.5. Testing a Project with cargo

This example assumes that you have successfully built the Rust project helloworld according to Example 2.2, “Building a Project using cargo”.

Change to the directory helloworld, and edit the file src/main.rs so that it contains the following source code:

fn main() {
    println!("Hello, world!");
}

#[test]
fn my_test() {
    assert_eq!(21+21, 42);
}

fn main() {
    println!("Hello, world!");
}

#[test]
fn my_test() {
    assert_eq!(21+21, 42);
}

Copy to Clipboard

Toggle word wrap

The function my_test marked as a test has been added.

Save the file, and run the test:

For Red Hat Enterprise Linux 7:

scl enable rust-toolset-1.35 'cargo test'

$ scl enable rust-toolset-1.35 'cargo test'
   Compiling helloworld v0.1.0 (file:///home/vslavik/Documentation/rusttest/helloworld)
    Finished dev [unoptimized + debuginfo] target(s) in 0.26 secs
     Running target/debug/deps/helloworld-9dd6b83647b49aec

running 1 test
test my_test ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured

Copy to Clipboard

Toggle word wrap

For Red Hat Enterprise Linux 8:

cargo test

$ cargo test
   Compiling helloworld v0.1.0 (file:///home/vslavik/Documentation/rusttest/helloworld)
    Finished dev [unoptimized + debuginfo] target(s) in 0.26 secs
     Running target/debug/deps/helloworld-9dd6b83647b49aec

running 1 test
test my_test ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured

Copy to Clipboard

Toggle word wrap

cargo first rebuilds the project, and then runs the tests found in the project. The test my_test has been succesfully passed.

2.7. Configuring Project Dependencies
Copier lien

To specify dependencies for a cargo project, edit the file Cargo.toml in the project directory. The section [dependencies] contains a list of the project’s dependencies. Each dependency is listed on a new line in the following format:

crate_name = version

crate_name = version

Copy to Clipboard

Toggle word wrap

Rust code packages are called crates.

Example 2.6. Adding Dependency to a Project and Building it with cargo

This example assumes that you have successfully built the Rust project helloworld according to Example 2.2, “Building a Project using cargo”.

Change to the directory helloworld and edit the file src/main.rs so that it contains the following source code:

extern crate time;

fn main() {
    println!("Hello, world!");
    println!("Time is: {}", time::now().rfc822());
}

extern crate time;

fn main() {
    println!("Hello, world!");
    println!("Time is: {}", time::now().rfc822());
}

Copy to Clipboard

Toggle word wrap

The code now requires an external crate time. Add this dependency to project configuration by editing the file Cargo.toml so that it contains the following code:

[package]
name = "helloworld"
version = "0.1.0"
authors = ["Your Name <yourname@example.com>"]

[dependencies]
time = "0.1"

[package]
name = "helloworld"
version = "0.1.0"
authors = ["Your Name <yourname@example.com>"]

[dependencies]
time = "0.1"

Copy to Clipboard

Toggle word wrap

Run the cargo run command to build the project and run the resulting executable file:

For Red Hat Enterprise Linux 7:

scl enable rust-toolset-1.35 'cargo run'

$ scl enable rust-toolset-1.35 'cargo run'
    Updating registry `https://github.com/rust-lang/crates.io-index`
 Downloading time v0.1.38
 Downloading libc v0.2.32
    Finished dev [unoptimized + debuginfo] target(s) in 0.0 secs
     Running `target/debug/helloworld`
Hello, world!
Time is: Fri, 13 Oct 2017 11:08:57

Copy to Clipboard

Toggle word wrap

For Red Hat Enterprise Linux 8:

cargo run

$ cargo run
    Updating registry `https://github.com/rust-lang/crates.io-index`
 Downloading time v0.1.38
 Downloading libc v0.2.32
    Finished dev [unoptimized + debuginfo] target(s) in 0.0 secs
     Running `target/debug/helloworld`
Hello, world!
Time is: Fri, 13 Oct 2017 11:08:57

Copy to Clipboard

Toggle word wrap

cargo downloads the time crate and its dependencies (crate libc), stores them locally, builds all of the project source code including the dependency crates, and finally runs the resulting executable.

Additional Resources

Specifying Dependencies — official cargo documentation.

2.8. Building Project Documentation
Copier lien

Note

Consider using cargo doc over rustdoc. The command cargo doc utilizes the rustdoc utility.

Note

cargo doc extracts documentation comments only for public functions, variables and members.

Rust code can contain comments marked for extraction into documentation. The comments support the Markdown language.

To build project documentation using the cargo tool, change to the project directory and run cargo tool:

For Red Hat Enterprise Linux 7:

scl enable rust-toolset-1.35 'cargo doc --no-deps'

$ scl enable rust-toolset-1.35 'cargo doc --no-deps'

Copy to Clipboard

Toggle word wrap

For Red Hat Enterprise Linux 8:
```
cargo doc --no-deps
```
```
$ cargo doc --no-deps
```
Copy to Clipboard Toggle word wrap

This extracts documentation stored from the special comments in the source code of your project and writes the documentation in HTML format.

Omit the --no-deps option to include dependencies in the generated documentation, including third party libraries.
Add the --open option to open the generated documentation in your browser.

Example 2.7. Building Project Documentation

This example assumes that you have successfully built the Rust project helloworld with dependencies, according to Example 2.6, “Adding Dependency to a Project and Building it with cargo”.

Change to the directory helloworld and edit the file src/main.rs so that it contains the following source code:

//! This is a hello-world program.
extern crate time;

/// Prints a greeting to `stdout`.
pub fn print_output() {
    println!("Hello, world!");
    println!("Time is: {}", time::now().rfc822());
}

/// The program entry point.
fn main() {
    print_output();
}

//! This is a hello-world program.
extern crate time;

/// Prints a greeting to `stdout`.
pub fn print_output() {
    println!("Hello, world!");
    println!("Time is: {}", time::now().rfc822());
}

/// The program entry point.
fn main() {
    print_output();
}

Copy to Clipboard

Toggle word wrap

The code now contains a public function print_output(). The whole helloworld program, the print_output() function, and the main() function have documentation comments.

Run the cargo doc command to build the project documentation:

For Red Hat Enterprise Linux 7:

scl enable rust-toolset-1.35 'cargo doc --no-deps'

$ scl enable rust-toolset-1.35 'cargo doc --no-deps'
 Documenting helloworld v0.1.0 (file:///home/vslavik/helloworld)
    Finished dev [unoptimized + debuginfo] target(s) in 0.31 secs

Copy to Clipboard

Toggle word wrap

For Red Hat Enterprise Linux 8:

cargo doc --no-deps

$ cargo doc --no-deps
 Documenting helloworld v0.1.0 (file:///home/vslavik/helloworld)
    Finished dev [unoptimized + debuginfo] target(s) in 0.31 secs

Copy to Clipboard

Toggle word wrap

Install tree tool (Available in the default Red Hat Enterprise Linux repositories.), if not already installed:

yum install tree

# yum install tree

Copy to Clipboard

Toggle word wrap

Examine the result:

tree

$ tree
.
├── Cargo.lock
├── Cargo.toml
├── src
│   └── main.rs
└── target
...
    └── doc
...
        ├── helloworld
        │   ├── fn.print_output.html
        │   ├── index.html
        │   ├── print_output.v.html
        │   └── sidebar-items.js
...
        └── src
            └── helloworld
                └── main.rs.html

12 directories, 32 files

Copy to Clipboard

Toggle word wrap

cargo builds the project documentation. To view the documentation, open the file target/doc/helloworld/index.html in your browser. The generated documentation does not contain any mention of the main() function, because it is not public.

Run the cargo doc command without the --no-deps option to build the project documentation, including the dependency libraries time and libc:

For Red Hat Enterprise Linux 7:

scl enable rust-toolset-1.35 'cargo doc'

$ scl enable rust-toolset-1.35 'cargo doc'
 Documenting libc v0.2.32
 Documenting time v0.1.38
 Documenting helloworld v0.1.0 (file:///home/vslavik/helloworld)
    Finished dev [unoptimized + debuginfo] target(s) in 3.41 secs

Copy to Clipboard

Toggle word wrap

For Red Hat Enterprise Linux 8:

cargo doc

$ cargo doc
 Documenting libc v0.2.32
 Documenting time v0.1.38
 Documenting helloworld v0.1.0 (file:///home/vslavik/helloworld)
    Finished dev [unoptimized + debuginfo] target(s) in 3.41 secs

Copy to Clipboard

Toggle word wrap

Examine the resulting folder structure with tree command:

tree
ls -d target/doc/*/

$ tree
...
92 directories, 11804 files
$ ls -d target/doc/*/
target/doc/helloworld/  target/doc/implementors/  target/doc/libc/  target/doc/src/  target/doc/time/

Copy to Clipboard

Toggle word wrap

The resulting documentation now covers also the dependency libraries time and libc, with each present as another subdirectory in the target/doc/ directory.

Additional Resources

A detailed description of the cargo doc tool and its features is beyond the scope of this book. For more information, see the resources listed below.

Making Useful Documentation Comments from the official Rust Programming Language documentation.

2.9. Vendoring Project Dependencies
Copier lien

Vendoring project dependencies means creating a local copy of the dependencies for offline redistribution and reuse. Vendored dependencies can be used by the cargo build tool without any connection to the internet.

The cargo vendor command for vendoring dependencies is supplied by the cargo plug-in cargo-vendor.

To install cargo-vendor 0.1.23 :

For Red Hat Enterprise Linux 7:
```
yum install rust-toolset-1.35-cargo-vendor
```
```
# yum install rust-toolset-1.35-cargo-vendor
```
Copy to Clipboard Toggle word wrap
For Red Hat Enterprise Linux 8:
```
dnf install cargo-vendor
```
```
# dnf install cargo-vendor
```
Copy to Clipboard Toggle word wrap

To vendor dependencies for a cargo project, change to the project directory and run the cargo tool as follows:

For Red Hat Enterprise Linux 7:
```
scl enable rust-toolset-1.35 'cargo vendor'
```
```
$ scl enable rust-toolset-1.35 'cargo vendor'
```
Copy to Clipboard Toggle word wrap
For Red Hat Enterprise Linux 8:
```
cargo vendor
```
```
$ cargo vendor
```
Copy to Clipboard Toggle word wrap

This creates a directory vendor and downloads sources of all dependencies to this directory. Additional configuration steps are printed to command line.

The cargo vendor command gathers the dependencies for a platform-independent result. Dependency crates for all potential target platforms are downloaded.

Important

The cargo vendor command is an experimental, unofficial plug-in for the cargo tool.

Example 2.8. Vendoring Project Dependencies

This example assumes that you have successfully built the Rust project helloworld with dependencies, according to Example 2.6, “Adding Dependency to a Project and Building it with cargo”.

Change to the directory helloworld and run the cargo vendor command to vendor the project with dependencies:

For Red Hat Enterprise Linux 7:

scl enable rust-toolset-1.35 'cargo vendor'

$ scl enable rust-toolset-1.35 'cargo vendor'
 Downloading kernel32-sys v0.2.2
 Downloading redox_syscall v0.1.31
 Downloading winapi-build v0.1.1
 Downloading winapi v0.2.8
   Vendoring kernel32-sys v0.2.2 (/home/vslavik/.cargo/registry/src/github.com-1ecc6299db9ec823/kernel32-sys-0.2.2) to vendor/kernel32-sys
   Vendoring libc v0.2.32 (/home/vslavik/.cargo/registry/src/github.com-1ecc6299db9ec823/libc-0.2.32) to vendor/libc
   Vendoring redox_syscall v0.1.31 (/home/vslavik/.cargo/registry/src/github.com-1ecc6299db9ec823/redox_syscall-0.1.31) to vendor/redox_syscall
   Vendoring time v0.1.38 (/home/vslavik/.cargo/registry/src/github.com-1ecc6299db9ec823/time-0.1.38) to vendor/time
   Vendoring winapi v0.2.8 (/home/vslavik/.cargo/registry/src/github.com-1ecc6299db9ec823/winapi-0.2.8) to vendor/winapi
   Vendoring winapi-build v0.1.1 (/home/vslavik/.cargo/registry/src/github.com-1ecc6299db9ec823/winapi-build-0.1.1) to vendor/winapi-build
To use vendored sources, add this to your .cargo/config for this project:

    [source.crates-io]
    replace-with = "vendored-sources"

    [source.vendored-sources]
    directory = "/home/vslavik/helloworld/vendor"

Copy to Clipboard

Toggle word wrap

For Red Hat Enterprise Linux 8:
```
cargo vendor
```
```
$ cargo vendor
```
Copy to Clipboard Toggle word wrap

Examine the result:

ls
tree vendor

$ ls
Cargo.lock  Cargo.toml  src  target  vendor
$ tree vendor
vendor
├── kernel32-sys
│   ├── build.rs
│   ├── Cargo.toml
│   ├── README.md
│   └── src
│       └── lib.rs
├── libc
│   ├── appveyor.yml
│   ├── Cargo.toml
...
75 directories, 319 files

Copy to Clipboard

Toggle word wrap

The vendor directory contains copies of all the dependency crates needed to build the helloworld program. Note that the crates for building the project on the Windows operating system have been vendored, too, despite running this command on Red Hat Enterprise Linux.

Note

The tree tool is available from the default Red Hat Enterprise Linux repositories. To install it:

yum install tree

# yum install tree

Copy to Clipboard

Toggle word wrap

2.10. Additional Resources
Copier lien

A detailed description of the cargo tool and its features is beyond the scope of this book. For more information, see the resources listed below.

Cargo Documentation

cargo(1) — The manual page for the cargo tool provides detailed information on its usage. To display the manual page for the version included in Rust Toolset:
- For Red Hat Enterprise Linux 7:
  $ scl enable rust-toolset-1.35 'man cargo'
  Copy to Clipboard Toggle word wrap
- For Red Hat Enterprise Linux 8:
  $ man cargo
  Copy to Clipboard Toggle word wrap
Cargo, Rust’s Package Manager HTML book is provided as a package:
- On Red Hat Enterprise Linux 7:
  # yum install rust-toolset-1.35-cargo-doc
  Copy to Clipboard Toggle word wrap
  The HTML is available at /opt/rh/rust-toolset-1.35/usr/share/doc/cargo/html/index.html
- On Red Hat Enterprise Linux 8:
  # yum install cargo-doc
  Copy to Clipboard Toggle word wrap
  The HTML is available at /usr/share/doc/cargo/html/index.html

Online Cargo Documentation

Official Cargo Guide

Ce contenu n'est pas disponible dans la langue sélectionnée.

2.1. Installing cargo
Copier lien

2.2. Creating a New Project
Copier lien

2.3. Building a Project
Copier lien

2.4. Checking a Program
Copier lien

2.5. Running a Program
Copier lien

2.6. Running Project Tests
Copier lien

2.7. Configuring Project Dependencies
Copier lien

Additional Resources

2.8. Building Project Documentation
Copier lien

Additional Resources

2.9. Vendoring Project Dependencies
Copier lien

2.10. Additional Resources
Copier lien

Cargo Documentation

Online Cargo Documentation

See Also

Apprendre

Essayez, achetez et vendez

Communautés

À propos de la documentation Red Hat

Rendre l’open source plus inclusif

À propos de Red Hat

Theme

Red Hat legal and privacy links

Red Hat legal and privacy links

Ce contenu n'est pas disponible dans la langue sélectionnée.

Chapter 2. cargo

2.1. Installing cargoCopier lienLien copié sur presse-papiers!

2.2. Creating a New ProjectCopier lienLien copié sur presse-papiers!

2.3. Building a ProjectCopier lienLien copié sur presse-papiers!

2.4. Checking a ProgramCopier lienLien copié sur presse-papiers!

2.5. Running a ProgramCopier lienLien copié sur presse-papiers!

2.6. Running Project TestsCopier lienLien copié sur presse-papiers!

2.7. Configuring Project DependenciesCopier lienLien copié sur presse-papiers!

Additional Resources

2.8. Building Project DocumentationCopier lienLien copié sur presse-papiers!

Additional Resources

2.9. Vendoring Project DependenciesCopier lienLien copié sur presse-papiers!

2.10. Additional ResourcesCopier lienLien copié sur presse-papiers!

Cargo Documentation

Online Cargo Documentation

See Also

Apprendre

Essayez, achetez et vendez

Communautés

À propos de la documentation Red Hat

Rendre l’open source plus inclusif

À propos de Red Hat

Theme

Red Hat legal and privacy links

Red Hat legal and privacy links

2.1. Installing cargo
Copier lien

2.2. Creating a New Project
Copier lien

2.3. Building a Project
Copier lien

2.4. Checking a Program
Copier lien

2.5. Running a Program
Copier lien

2.6. Running Project Tests
Copier lien

2.7. Configuring Project Dependencies
Copier lien

2.8. Building Project Documentation
Copier lien

2.9. Vendoring Project Dependencies
Copier lien

2.10. Additional Resources
Copier lien