24 lines
1.4 KiB
HTML
24 lines
1.4 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
<head>
|
||
<meta charset="UTF-8">
|
||
<title>Extending Cargo with Custom Commands</title>
|
||
</head>
|
||
<body>
|
||
<h2 id="extending-cargo-with-custom-commands"><a class="header" href="#extending-cargo-with-custom-commands">Extending Cargo with Custom Commands</a></h2>
|
||
<p>Cargo is designed so that you can extend it with new subcommands without having
|
||
to modify it. If a binary in your <code>$PATH</code> is named <code>cargo-something</code>, you can
|
||
run it as if it were a Cargo subcommand by running <code>cargo something</code>. Custom
|
||
commands like this are also listed when you run <code>cargo --list</code>. Being able to
|
||
use <code>cargo install</code> to install extensions and then run them just like the
|
||
built-in Cargo tools is a super-convenient benefit of Cargo’s design!</p>
|
||
<h2 id="summary"><a class="header" href="#summary">Summary</a></h2>
|
||
<p>Sharing code with Cargo and <a href="https://crates.io/">crates.io</a><!-- ignore --> is
|
||
part of what makes the Rust ecosystem useful for many different tasks. Rust’s
|
||
standard library is small and stable, but crates are easy to share, use, and
|
||
improve on a timeline different from that of the language. Don’t be shy about
|
||
sharing code that’s useful to you on <a href="https://crates.io/">crates.io</a><!-- ignore
|
||
-->; it’s likely that it will be useful to someone else as well!</p>
|
||
</body>
|
||
</html>
|