2017-03-12 15:31:28 +08:00
|
|
|
|
<!DOCTYPE HTML>
|
|
|
|
|
|
<html lang="en">
|
|
|
|
|
|
<head>
|
|
|
|
|
|
<meta charset="UTF-8">
|
|
|
|
|
|
<title>Cargo 工作空间 - Rust 程序设计语言 简体中文版</title>
|
|
|
|
|
|
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
|
|
|
|
|
|
<meta name="description" content="Rust 程序设计语言 简体中文版">
|
|
|
|
|
|
<meta name="viewport" content="width=device-width, initial-scale=1">
|
|
|
|
|
|
|
|
|
|
|
|
<base href="">
|
|
|
|
|
|
|
|
|
|
|
|
<link rel="stylesheet" href="book.css">
|
|
|
|
|
|
<link href='https://fonts.googleapis.com/css?family=Open+Sans:300italic,400italic,600italic,700italic,800italic,400,300,600,700,800' rel='stylesheet' type='text/css'>
|
|
|
|
|
|
|
|
|
|
|
|
<link rel="shortcut icon" href="favicon.png">
|
|
|
|
|
|
|
|
|
|
|
|
<!-- Font Awesome -->
|
|
|
|
|
|
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.3.0/css/font-awesome.min.css">
|
|
|
|
|
|
|
|
|
|
|
|
<link rel="stylesheet" href="highlight.css">
|
|
|
|
|
|
<link rel="stylesheet" href="tomorrow-night.css">
|
|
|
|
|
|
|
|
|
|
|
|
<!-- MathJax -->
|
|
|
|
|
|
<script type="text/javascript" src="https://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML"></script>
|
|
|
|
|
|
|
|
|
|
|
|
<!-- Fetch JQuery from CDN but have a local fallback -->
|
|
|
|
|
|
<script src="https://code.jquery.com/jquery-2.1.4.min.js"></script>
|
|
|
|
|
|
<script>
|
|
|
|
|
|
if (typeof jQuery == 'undefined') {
|
|
|
|
|
|
document.write(unescape("%3Cscript src='jquery.js'%3E%3C/script%3E"));
|
|
|
|
|
|
}
|
|
|
|
|
|
</script>
|
|
|
|
|
|
</head>
|
|
|
|
|
|
<body class="light">
|
|
|
|
|
|
<!-- Set the theme before any content is loaded, prevents flash -->
|
|
|
|
|
|
<script type="text/javascript">
|
|
|
|
|
|
var theme = localStorage.getItem('theme');
|
|
|
|
|
|
if (theme == null) { theme = 'light'; }
|
|
|
|
|
|
$('body').removeClass().addClass(theme);
|
|
|
|
|
|
</script>
|
|
|
|
|
|
|
|
|
|
|
|
<!-- Hide / unhide sidebar before it is displayed -->
|
|
|
|
|
|
<script type="text/javascript">
|
|
|
|
|
|
var sidebar = localStorage.getItem('sidebar');
|
|
|
|
|
|
if (sidebar === "hidden") { $("html").addClass("sidebar-hidden") }
|
|
|
|
|
|
else if (sidebar === "visible") { $("html").addClass("sidebar-visible") }
|
|
|
|
|
|
</script>
|
|
|
|
|
|
|
|
|
|
|
|
<div id="sidebar" class="sidebar">
|
2017-05-31 23:48:57 +08:00
|
|
|
|
<ul class="chapter"><li><a href="ch01-00-introduction.html"><strong>1.</strong> 介绍</a></li><li><ul class="section"><li><a href="ch01-01-installation.html"><strong>1.1.</strong> 安装</a></li><li><a href="ch01-02-hello-world.html"><strong>1.2.</strong> Hello, World!</a></li></ul></li><li><a href="ch02-00-guessing-game-tutorial.html"><strong>2.</strong> 猜猜看教程</a></li><li><a href="ch03-00-common-programming-concepts.html"><strong>3.</strong> 通用编程概念</a></li><li><ul class="section"><li><a href="ch03-01-variables-and-mutability.html"><strong>3.1.</strong> 变量和可变性</a></li><li><a href="ch03-02-data-types.html"><strong>3.2.</strong> 数据类型</a></li><li><a href="ch03-03-how-functions-work.html"><strong>3.3.</strong> 函数如何工作</a></li><li><a href="ch03-04-comments.html"><strong>3.4.</strong> 注释</a></li><li><a href="ch03-05-control-flow.html"><strong>3.5.</strong> 控制流</a></li></ul></li><li><a href="ch04-00-understanding-ownership.html"><strong>4.</strong> 认识所有权</a></li><li><ul class="section"><li><a href="ch04-01-what-is-ownership.html"><strong>4.1.</strong> 什么是所有权</a></li><li><a href="ch04-02-references-and-borrowing.html"><strong>4.2.</strong> 引用 & 借用</a></li><li><a href="ch04-03-slices.html"><strong>4.3.</strong> Slices</a></li></ul></li><li><a href="ch05-00-structs.html"><strong>5.</strong> 结构体</a></li><li><ul class="section"><li><a href="ch05-01-method-syntax.html"><strong>5.1.</strong> 方法语法</a></li></ul></li><li><a href="ch06-00-enums.html"><strong>6.</strong> 枚举和模式匹配</a></li><li><ul class="section"><li><a href="ch06-01-defining-an-enum.html"><strong>6.1.</strong> 定义枚举</a></li><li><a href="ch06-02-match.html"><strong>6.2.</strong> <code>match</code>控制流运算符</a></li><li><a href="ch06-03-if-let.html"><strong>6.3.</strong> <code>if let</code>简单控制流</a></li></ul></li><li><a href="ch07-00-modules.html"><strong>7.</strong> 模块</a></li><li><ul class="section"><li><a href="ch07-01-mod-and-the-filesystem.html"><strong>7.1.</strong> <code>mod</code>和文件系统</a></li><li><a href="ch07-02-controlling-visibility-with-pub.html"><strong>7.2.</strong> 使用<code>pub</code>控制可见性</a></li><li><a href="ch07-03-importing-names-with-use.html"><strong>7.3.</strong> 使用<code>use</code>导入命名</a></li></ul></li><li><a href="ch08-00-common-collections.html"><strong>8.</strong> 通用集合类型</a></li><li><ul class="section"><li><a href="ch08-01-vectors.html"><strong>8.1.</strong> vector</a></li><li><a href="ch08-02-strings.html"><strong>8.2.</strong> 字符串</a></li><li><a href="ch08-03-hash-maps.html"><strong>8.3.</strong> 哈希 map</a></li></ul></li><li><a href="ch09-00-error-handling.html"><strong>9.</strong> 错误处理</a></li><li><ul class="section"><li><a href="ch09-01-unrecoverable-errors-with-panic.html"><strong>9.1.</strong> <code>panic!</code>与不可恢复的错误</a></li><li><a href="ch09-02-recoverable-errors-with-result.html"><strong>9.2.</strong> <code>Result</code>与可恢复的错误</a></li><li><a href="ch09-03-to-panic-or-not-to-panic.html"><strong>9.3.</strong> <code>panic!</code>还是不<code>panic!</code></a></li></ul></li><li><a href="ch10-00-generics.html"><strong>10.</strong> 泛型、trait 和生命周期</a></li><li><ul class="section"><li><a href="ch10-01-syntax.html"><strong>10.1.</strong> 泛型数据类型</a></li><li><a href="ch10-02-traits.html"><strong>10.2.</strong> trait：定义共享的行为</a></li><li><a href="ch10-03-lifetime-syntax.html"><strong>10.3.</strong> 生命周期与引用有效性</a></li></ul></li><li><a href="ch11-00-testing.html"><strong>11.</strong> 测试</a></li><li><ul class="section"><li><a href="ch11-01-writing-tests.html"><strong>11.1.</strong> 编写测试</a></li><li><a href="ch11-02-running-tests.html"><strong>11.2.</strong> 运行测试</a></li><li><a href="ch11-03-test-organization.html"><strong>11.3.</strong> 测试的组织结构</a></li></ul></li><li><a href="ch12-00-an-io-project.h
|
2017-03-12 15:31:28 +08:00
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
|
|
<div id="page-wrapper" class="page-wrapper">
|
|
|
|
|
|
|
|
|
|
|
|
<div class="page">
|
|
|
|
|
|
<div id="menu-bar" class="menu-bar">
|
|
|
|
|
|
<div class="left-buttons">
|
|
|
|
|
|
<i id="sidebar-toggle" class="fa fa-bars"></i>
|
|
|
|
|
|
<i id="theme-toggle" class="fa fa-paint-brush"></i>
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
|
|
<h1 class="menu-title">Rust 程序设计语言 简体中文版</h1>
|
|
|
|
|
|
|
|
|
|
|
|
<div class="right-buttons">
|
|
|
|
|
|
<i id="print-button" class="fa fa-print" title="Print this book"></i>
|
|
|
|
|
|
</div>
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
|
|
<div id="content" class="content">
|
|
|
|
|
|
<a class="header" href="#cargo-工作空间" name="cargo-工作空间"><h2>Cargo 工作空间</h2></a>
|
|
|
|
|
|
<blockquote>
|
|
|
|
|
|
<p><a href="https://github.com/rust-lang/book/blob/master/second-edition/src/ch14-03-cargo-workspaces.md">ch14-03-cargo-workspaces.md</a>
|
|
|
|
|
|
<br>
|
|
|
|
|
|
commit d945f6d4046f4fc3c09326213100492790aebb45</p>
|
|
|
|
|
|
</blockquote>
|
|
|
|
|
|
<p>第十二章中，我们构建一个包含二进制 crate 和库 crate 的包。不过如果库 crate 继续变得更大而我们想要进一步将包拆分为多个库 crate 呢？随着包增长，拆分出其主要组件将是非常有帮助的。对于这种情况，Cargo 提供了一个叫<strong>工作空间</strong>（<em>workspaces</em>）的功能，它可以帮助我们管理多个相关的并行开发的包。</p>
|
|
|
|
|
|
<p><strong>工作空间</strong>是一系列的包都共享同样的 <em>Cargo.lock</em> 和输出目录。让我们使用工作空间创建一个项目，这是我们熟悉的所以就可以关注工作空间的结构了。这里有一个二进制项目它使用了两个库：一个会提供<code>add_one</code>方法而第二个会提供<code>add_two</code>方法。让我们为这个二进制项目创建一个新 crate 作为开始：</p>
|
|
|
|
|
|
<pre><code>$ cargo new --bin adder
|
|
|
|
|
|
Created binary (application) `adder` project
|
|
|
|
|
|
$ cd adder
|
|
|
|
|
|
</code></pre>
|
|
|
|
|
|
<p>需要修改二进制包的 <em>Cargo.toml</em> 来告诉 Cargo 包<code>adder</code>是一个工作空间。再文件末尾增加如下：</p>
|
|
|
|
|
|
<pre><code class="language-toml">[workspace]
|
|
|
|
|
|
</code></pre>
|
|
|
|
|
|
<p>类似于很多 Cargo 的功能，工作空间支持配置惯例：只要遵循这些惯例就无需再增加任何配置了。这个惯例是任何作为子目录依赖的 crate 将是工作空间的一部分。让我们像这样在 <em>Cargo.toml</em> 中的<code>[dependencies]</code>增加一个<code>adder</code> crate 的路径依赖：</p>
|
|
|
|
|
|
<pre><code class="language-toml">[dependencies]
|
|
|
|
|
|
add-one = { path = "add-one" }
|
|
|
|
|
|
</code></pre>
|
|
|
|
|
|
<p>如果增加依赖但没有指定<code>path</code>，这将是一个不位于工作空间的正常的依赖。</p>
|
|
|
|
|
|
<p>接下来，在<code>adder</code>目录中生成<code>add-one</code> crate：</p>
|
|
|
|
|
|
<pre><code>$ cargo new add-one
|
|
|
|
|
|
Created library `add-one` project
|
|
|
|
|
|
</code></pre>
|
|
|
|
|
|
<p>现在<code>adder</code>目录应该有如下目录和文件：</p>
|
|
|
|
|
|
<pre><code>├── Cargo.toml
|
|
|
|
|
|
├── add-one
|
|
|
|
|
|
│ ├── Cargo.toml
|
|
|
|
|
|
│ └── src
|
|
|
|
|
|
│ └── lib.rs
|
|
|
|
|
|
└── src
|
|
|
|
|
|
└── main.rs
|
|
|
|
|
|
</code></pre>
|
|
|
|
|
|
<p>在 <em>add-one/src/lib.rs</em> 中增加<code>add_one</code>函数的实现：</p>
|
|
|
|
|
|
<p><span class="filename">Filename: add-one/src/lib.rs</span></p>
|
|
|
|
|
|
<pre><code class="language-rust">pub fn add_one(x: i32) -> i32 {
|
|
|
|
|
|
x + 1
|
|
|
|
|
|
}
|
|
|
|
|
|
</code></pre>
|
|
|
|
|
|
<p>打开<code>adder</code>的 <em>src/main.rs</em> 并增加一行<code>extern crate</code>将新的<code>add-one</code>库引入作用域，并修改<code>main</code>函数来使用<code>add_one</code>函数：</p>
|
|
|
|
|
|
<pre><code class="language-rust,ignore">extern crate add_one;
|
|
|
|
|
|
|
|
|
|
|
|
fn main() {
|
|
|
|
|
|
let num = 10;
|
|
|
|
|
|
println!("Hello, world! {} plus one is {}!", num, add_one::add_one(num));
|
|
|
|
|
|
}
|
|
|
|
|
|
</code></pre>
|
|
|
|
|
|
<p>让我们构建一下！</p>
|
|
|
|
|
|
<pre><code>$ cargo build
|
|
|
|
|
|
Compiling add-one v0.1.0 (file:///projects/adder/add-one)
|
|
|
|
|
|
Compiling adder v0.1.0 (file:///projects/adder)
|
|
|
|
|
|
Finished debug [unoptimized + debuginfo] target(s) in 0.68 secs
|
|
|
|
|
|
</code></pre>
|
|
|
|
|
|
<p>注意在 <em>adder</em> 目录运行<code>cargo build</code>会构建这个 crate 和 <em>adder/add-one</em> 中的<code>add-one</code> crate，不过只创建一个 <em>Cargo.lock</em> 和一个 <em>target</em> 目录，他们都位于 <em>adder</em> 目录。试试你能否用相同的方式增加<code>add-two</code> crate。</p>
|
|
|
|
|
|
<p>假如我们想要在<code>add-one</code> crate 中使用<code>rand</code> crate。一如既往在<code>Cargo.toml</code>的<code>[dependencies]</code>部分增加这个 crate：</p>
|
|
|
|
|
|
<p><span class="filename">Filename: add-one/Cargo.toml</span></p>
|
|
|
|
|
|
<pre><code class="language-toml">[dependencies]
|
|
|
|
|
|
|
|
|
|
|
|
rand = "0.3.14"
|
|
|
|
|
|
</code></pre>
|
|
|
|
|
|
<p>如果在 <em>add-one/src/lib.rs</em> 中加上<code>extern crate rand;</code>后再运行<code>cargo build</code>，则会编译成功：</p>
|
|
|
|
|
|
<pre><code>$ cargo build
|
|
|
|
|
|
Updating registry `https://github.com/rust-lang/crates.io-index`
|
|
|
|
|
|
Downloading rand v0.3.14
|
|
|
|
|
|
...snip...
|
|
|
|
|
|
Compiling rand v0.3.14
|
|
|
|
|
|
Compiling add-one v0.1.0 (file:///projects/adder/add-one)
|
|
|
|
|
|
Compiling adder v0.1.0 (file:///projects/adder)
|
|
|
|
|
|
Finished debug [unoptimized + debuginfo] target(s) in 10.18 secs
|
|
|
|
|
|
</code></pre>
|
|
|
|
|
|
<p>现在 <em>Cargo.lock</em> 的顶部反映了<code>add-one</code>依赖<code>rand</code>这一事实。然而即使在工作空间的某处使用了<code>rand</code>，也不能在工作空间的其他 crate 使用它，除非在对应的 <em>Cargo.toml</em> 也增加<code>rand</code>的依赖。例如，如果在顶层的<code>adder</code> crate 的 <em>src/main.rs</em> 中增加<code>extern crate rand;</code>，将会出现一个错误：</p>
|
|
|
|
|
|
<pre><code>$ cargo build
|
|
|
|
|
|
Compiling adder v0.1.0 (file:///projects/adder)
|
|
|
|
|
|
error[E0463]: can't find crate for `rand`
|
|
|
|
|
|
--> src/main.rs:1:1
|
|
|
|
|
|
|
|
|
|
|
|
|
1 | extern crate rand;
|
|
|
|
|
|
| ^^^^^^^^^^^^^^^^^^^ can't find crate
|
|
|
|
|
|
</code></pre>
|
|
|
|
|
|
<p>为了修复这个错误，修改顶层的 <em>Cargo.toml</em> 并表明<code>rand</code>是<code>adder</code> crate 的一个依赖。</p>
|
|
|
|
|
|
<p>作为另一个提高，为 crate 中的<code>add_one::add_one</code>函数增加一个测试：</p>
|
|
|
|
|
|
<p><span class="filename">Filename: add-one/src/lib.rs</span></p>
|
|
|
|
|
|
<pre><code class="language-rust">pub fn add_one(x: i32) -> i32 {
|
|
|
|
|
|
x + 1
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
#[cfg(test)]
|
|
|
|
|
|
mod tests {
|
|
|
|
|
|
use super::*;
|
|
|
|
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
|
|
fn it_works() {
|
|
|
|
|
|
assert_eq!(3, add_one(2));
|
|
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
</code></pre>
|
|
|
|
|
|
<p>现在在顶层的 <em>adder</em> 目录运行<code>cargo test</code>：</p>
|
|
|
|
|
|
<pre><code>$ cargo test
|
|
|
|
|
|
Compiling adder v0.1.0 (file:///projects/adder)
|
|
|
|
|
|
Finished debug [unoptimized + debuginfo] target(s) in 0.27 secs
|
|
|
|
|
|
Running target/debug/adder-f0253159197f7841
|
|
|
|
|
|
|
|
|
|
|
|
running 0 tests
|
|
|
|
|
|
|
|
|
|
|
|
test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured
|
|
|
|
|
|
</code></pre>
|
2017-04-24 23:03:13 +08:00
|
|
|
|
<p>等等，零个测试？我们不是刚增加了一个吗？如果我们观察输出，就不难发现在工作空间中的<code>cargo test</code>只运行顶层 crate 的测试。为了运行其他 crate 的测试，需要使用<code>-p</code>参数来表明我们希望运行指定包的测试：</p>
|
2017-03-12 15:31:28 +08:00
|
|
|
|
<pre><code>$ cargo test -p add-one
|
|
|
|
|
|
Finished debug [unoptimized + debuginfo] target(s) in 0.0 secs
|
|
|
|
|
|
Running target/debug/deps/add_one-abcabcabc
|
|
|
|
|
|
|
|
|
|
|
|
running 1 test
|
|
|
|
|
|
test tests::it_works ... ok
|
|
|
|
|
|
|
|
|
|
|
|
test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured
|
|
|
|
|
|
|
|
|
|
|
|
Doc-tests add-one
|
|
|
|
|
|
|
|
|
|
|
|
running 0 tests
|
|
|
|
|
|
|
|
|
|
|
|
test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured
|
|
|
|
|
|
</code></pre>
|
|
|
|
|
|
<p>类似的，如果选择将工作空间发布到 crates.io，其中的每一个包都需要单独发布。</p>
|
|
|
|
|
|
<p>随着项目增长，考虑使用工作空间：每一个更小的组件比一大块代码要容易理解。将 crate 保持在工作空间中易于协调他们的改变，如果他们一起运行并经常需要同时被修改的话。</p>
|
|
|
|
|
|
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
|
|
<!-- Mobile navigation buttons -->
|
|
|
|
|
|
|
|
|
|
|
|
<a href="ch14-02-publishing-to-crates-io.html" class="mobile-nav-chapters previous">
|
|
|
|
|
|
<i class="fa fa-angle-left"></i>
|
|
|
|
|
|
</a>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<a href="ch14-04-installing-binaries.html" class="mobile-nav-chapters next">
|
|
|
|
|
|
<i class="fa fa-angle-right"></i>
|
|
|
|
|
|
</a>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<a href="ch14-02-publishing-to-crates-io.html" class="nav-chapters previous" title="You can navigate through the chapters using the arrow keys">
|
|
|
|
|
|
<i class="fa fa-angle-left"></i>
|
|
|
|
|
|
</a>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<a href="ch14-04-installing-binaries.html" class="nav-chapters next" title="You can navigate through the chapters using the arrow keys">
|
|
|
|
|
|
<i class="fa fa-angle-right"></i>
|
|
|
|
|
|
</a>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<!-- Local fallback for Font Awesome -->
|
|
|
|
|
|
<script>
|
|
|
|
|
|
if ($(".fa").css("font-family") !== "FontAwesome") {
|
|
|
|
|
|
$('<link rel="stylesheet" type="text/css" href="_FontAwesome/css/font-awesome.css">').prependTo('head');
|
|
|
|
|
|
}
|
|
|
|
|
|
</script>
|
|
|
|
|
|
|
|
|
|
|
|
<!-- Livereload script (if served using the cli tool) -->
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<script src="highlight.js"></script>
|
|
|
|
|
|
<script src="book.js"></script>
|
|
|
|
|
|
</body>
|
|
|
|
|
|
</html>
|
