@@ -80,7 +80,7 @@ virtual workspace will include all workspace members (equivalent to passing
80
80
81
81
<dt class =" option-term " id =" option-cargo-bench--p " ><a class =" option-anchor " href =" #option-cargo-bench--p " ></a ><code >-p</code > <em >spec</em >...</dt >
82
82
<dt class =" option-term " id =" option-cargo-bench---package " ><a class =" option-anchor " href =" #option-cargo-bench---package " ></a ><code >--package</code > <em >spec</em >...</dt >
83
- <dd class =" option-desc " >Benchmark only the specified packages. See <a href =" https://doc.rust-lang.org/ cargo/commands/cargo -pkgid.md " >cargo-pkgid(1)</a > for the
83
+ <dd class =" option-desc " >Benchmark only the specified packages. See <a href =" cargo-pkgid.html " >cargo-pkgid(1)</a > for the
84
84
SPEC format. This flag may be specified multiple times.</dd >
85
85
86
86
@@ -224,10 +224,10 @@ architecture. The general format of the triple is
224
224
<code >< ; arch> ;< ; sub> ; -< ; vendor> ; -< ; sys> ; -< ; abi> ; </code >. Run <code >rustc --print target-list</code > for a
225
225
list of supported targets.</p >
226
226
<p >This may also be specified with the <code >build.target</code >
227
- <a href =" https://doc.rust-lang.org/cargo /reference/config.html" >config value</a >.</p >
227
+ <a href =" .. /reference/config.html" >config value</a >.</p >
228
228
<p >Note that specifying this flag makes Cargo run in a different mode where the
229
229
target artifacts are placed in a separate directory. See the
230
- <a href =" https://doc.rust-lang.org/cargo /guide/build-cache.html" >build cache</a > documentation for more details.</dd >
230
+ <a href =" .. /guide/build-cache.html" >build cache</a > documentation for more details.</dd >
231
231
232
232
233
233
@@ -239,7 +239,7 @@ target artifacts are placed in a separate directory. See the
239
239
<dt class =" option-term " id =" option-cargo-bench---target-dir " ><a class =" option-anchor " href =" #option-cargo-bench---target-dir " ></a ><code >--target-dir</code > <em >directory</em ></dt >
240
240
<dd class =" option-desc " >Directory for all generated artifacts and intermediate files. May also be
241
241
specified with the <code >CARGO_TARGET_DIR</code > environment variable, or the
242
- <code >build.target-dir</code > <a href =" https://doc.rust-lang.org/cargo /reference/config.html" >config value</a >. Defaults
242
+ <code >build.target-dir</code > <a href =" .. /reference/config.html" >config value</a >. Defaults
243
243
to <code >target</code > in the root of the workspace.</dd >
244
244
245
245
@@ -260,7 +260,7 @@ passing `--nocapture` to the benchmark binaries:
260
260
<dd class =" option-desc " >Use verbose output. May be specified twice for " ; very verbose" ; output which
261
261
includes extra output such as dependency warnings and build script output.
262
262
May also be specified with the <code >term.verbose</code >
263
- <a href =" https://doc.rust-lang.org/cargo /reference/config.html" >config value</a >.</dd >
263
+ <a href =" .. /reference/config.html" >config value</a >.</dd >
264
264
265
265
266
266
<dt class =" option-term " id =" option-cargo-bench--q " ><a class =" option-anchor " href =" #option-cargo-bench--q " ></a ><code >-q</code ></dt >
@@ -277,7 +277,7 @@ terminal.</li>
277
277
<li ><code >never</code >: Never display colors.</li >
278
278
</ul >
279
279
<p >May also be specified with the <code >term.color</code >
280
- <a href =" https://doc.rust-lang.org/cargo /reference/config.html" >config value</a >.</dd >
280
+ <a href =" .. /reference/config.html" >config value</a >.</dd >
281
281
282
282
283
283
@@ -288,7 +288,7 @@ and consists of comma-separated values. Valid values:</p>
288
288
<li ><code >human</code > (default): Display in a human-readable text format.</li >
289
289
<li ><code >short</code >: Emit shorter, human-readable text messages.</li >
290
290
<li ><code >json</code >: Emit JSON messages to stdout. See
291
- <a href =" https://doc.rust-lang.org/cargo /reference/external-tools.html#json-messages" >the reference</a >
291
+ <a href =" .. /reference/external-tools.html#json-messages" >the reference</a >
292
292
for more details.</li >
293
293
<li ><code >json-diagnostic-short</code >: Ensure the <code >rendered</code > field of JSON messages contains
294
294
the " ; short" ; rendering from rustc.</li >
@@ -333,9 +333,9 @@ proceed without the network if possible.</p>
333
333
<p >Beware that this may result in different dependency resolution than online
334
334
mode. Cargo will restrict itself to crates that are downloaded locally, even
335
335
if there might be a newer version as indicated in the local copy of the index.
336
- See the <a href =" https://doc.rust-lang.org/ cargo/commands/cargo -fetch.md " >cargo-fetch(1)</a > command to download dependencies before going
336
+ See the <a href =" cargo-fetch.html " >cargo-fetch(1)</a > command to download dependencies before going
337
337
offline.</p >
338
- <p >May also be specified with the <code >net.offline</code > <a href =" https://doc.rust-lang.org/cargo /reference/config.html" >config value</a >.</dd >
338
+ <p >May also be specified with the <code >net.offline</code > <a href =" .. /reference/config.html" >config value</a >.</dd >
339
339
340
340
341
341
</dl >
@@ -374,7 +374,7 @@ Rust test harness runs benchmarks serially in a single thread.
374
374
<dt class =" option-term " id =" option-cargo-bench--j " ><a class =" option-anchor " href =" #option-cargo-bench--j " ></a ><code >-j</code > <em >N</em ></dt >
375
375
<dt class =" option-term " id =" option-cargo-bench---jobs " ><a class =" option-anchor " href =" #option-cargo-bench---jobs " ></a ><code >--jobs</code > <em >N</em ></dt >
376
376
<dd class =" option-desc " >Number of parallel jobs to run. May also be specified with the
377
- <code >build.jobs</code > <a href =" https://doc.rust-lang.org/cargo /reference/config.html" >config value</a >. Defaults to
377
+ <code >build.jobs</code > <a href =" .. /reference/config.html" >config value</a >. Defaults to
378
378
the number of CPUs.</dd >
379
379
380
380
@@ -393,7 +393,7 @@ are built with the `release` profiles when linked to binaries and benchmarks.
393
393
Dependencies use the ` release ` profile.
394
394
395
395
If you need a debug build of a benchmark, try building it with
396
- [ cargo-build(1)] ( cargo-build.md ) which will use the ` test ` profile which is by default
396
+ [ cargo-build(1)] ( cargo-build.html ) which will use the ` test ` profile which is by default
397
397
unoptimized and includes debug information. You can then run the debug-enabled
398
398
benchmark manually.
399
399
@@ -420,4 +420,4 @@ details on environment variables that Cargo reads.
420
420
cargo bench --bench bench_name -- modname::some_benchmark
421
421
422
422
## SEE ALSO
423
- [ cargo(1)] ( cargo.md ) , [ cargo-test(1)] ( cargo-test.md )
423
+ [ cargo(1)] ( cargo.html ) , [ cargo-test(1)] ( cargo-test.html )
0 commit comments