Update other docs to use cargo:: syntax

Signed-off-by: hi-rustin <rustin.liu@gmail.com>

Author: 0xPoe

src/cargo/core/compiler/custom_build.rs

@@ -150,7 +150,7 @@ pub struct BuildDeps {
     pub rerun_if_env_changed: Vec<String>,
 }
 
-/// Represents one of the instructions from `cargo:rustc-link-arg-*` build
+/// Represents one of the instructions from `cargo::rustc-link-arg-*` build
 /// script instruction family.
 ///
 /// In other words, indicates targets that custom linker arguments applies to.
@@ -160,19 +160,19 @@ pub struct BuildDeps {
 /// [1]: https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#cargorustc-link-argflag
 #[derive(Clone, Hash, Debug, PartialEq, Eq)]
 pub enum LinkArgTarget {
-    /// Represents `cargo:rustc-link-arg=FLAG`.
+    /// Represents `cargo::rustc-link-arg=FLAG`.
     All,
-    /// Represents `cargo:rustc-cdylib-link-arg=FLAG`.
+    /// Represents `cargo::rustc-cdylib-link-arg=FLAG`.
     Cdylib,
-    /// Represents `cargo:rustc-link-arg-bins=FLAG`.
+    /// Represents `cargo::rustc-link-arg-bins=FLAG`.
     Bin,
-    /// Represents `cargo:rustc-link-arg-bin=BIN=FLAG`.
+    /// Represents `cargo::rustc-link-arg-bin=BIN=FLAG`.
     SingleBin(String),
-    /// Represents `cargo:rustc-link-arg-tests=FLAG`.
+    /// Represents `cargo::rustc-link-arg-tests=FLAG`.
     Test,
-    /// Represents `cargo:rustc-link-arg-benches=FLAG`.
+    /// Represents `cargo::rustc-link-arg-benches=FLAG`.
     Bench,
-    /// Represents `cargo:rustc-link-arg-examples=FLAG`.
+    /// Represents `cargo::rustc-link-arg-examples=FLAG`.
     Example,
 }
 

src/doc/src/faq.md

@@ -242,7 +242,7 @@ Cargo has no way right now of after-the-fact debugging "why was that rebuilt?"
 
 Some issues we've seen historically which can cause crates to get rebuilt are:
 
-* A build script prints `cargo:rerun-if-changed=foo` where `foo` is a file that
+* A build script prints `cargo::rerun-if-changed=foo` where `foo` is a file that
   doesn't exist and nothing generates it. In this case Cargo will keep running
   the build script thinking it will generate the file but nothing ever does. The
   fix is to avoid printing `rerun-if-changed` in this scenario.
@@ -280,38 +280,38 @@ issue](https://github.com/rust-lang/cargo/issues/new)!
 
 Have you seen the error message above?
 
-This is one of the most annoying error message for Cargo users. There are several 
-situations may lead us to a version conflict. Below we'll walk through possible 
+This is one of the most annoying error message for Cargo users. There are several
+situations may lead us to a version conflict. Below we'll walk through possible
 causes and provide diagnostic techniques to help you out there:
 
-- The project and its dependencies use [links] to repeatedly link the local 
-  library. Cargo forbids linking two packages with the same native library, so 
-  even with multiple layers of dependencies it is not allowed. In this case, the 
-  error message will prompt: `Only one package in the dependency graph may specify 
-  the same links value`, you may need to manually check and delete duplicate link 
+- The project and its dependencies use [links] to repeatedly link the local
+  library. Cargo forbids linking two packages with the same native library, so
+  even with multiple layers of dependencies it is not allowed. In this case, the
+  error message will prompt: `Only one package in the dependency graph may specify
+  the same links value`, you may need to manually check and delete duplicate link
   values. The community also have [conventions in place] to alleviate this.
 
-- When depending on different crates in the project, if these crates use the same 
-  dependent library, but the version used is restricted, making it impossible to 
-  determine the correct version, it will also cause conflicts. The error message 
-  will prompt: `all possible versions conflict with previously selected packages`. 
+- When depending on different crates in the project, if these crates use the same
+  dependent library, but the version used is restricted, making it impossible to
+  determine the correct version, it will also cause conflicts. The error message
+  will prompt: `all possible versions conflict with previously selected packages`.
   You may need to modify the version requirements to make them consistent.
 
-- If there are multiple versions of dependencies in the project, when using 
-  [`direct-minimal-versions`], the minimum version requirements cannot be met, 
+- If there are multiple versions of dependencies in the project, when using
+  [`direct-minimal-versions`], the minimum version requirements cannot be met,
   which will cause conflicts. You may need to modify version requirements of your
   direct dependencies to meet the minimum SemVer version accordingly.
 
-- If the dependent crate does not have the features you choose, it will also 
-  cause conflicts. At this time, you need to check the dependent version and its 
+- If the dependent crate does not have the features you choose, it will also
+  cause conflicts. At this time, you need to check the dependent version and its
   features.
 
-- Conflicts may occur when merging branches or PRs, if there are non-trivial 
-  conflicts, you can reset all "yours" changes, fix all other conflicts in the 
-  branch, and then run some cargo command (like `cargo tree` or `cargo check`), 
-  which should re-update the lockfile with your own local changes. If you previously 
-  ran some `cargo update` commands in your branch, you can re-run them that this 
-  time. The community has been looking to resolve merge conflicts with `Cargo.lock` 
+- Conflicts may occur when merging branches or PRs, if there are non-trivial
+  conflicts, you can reset all "yours" changes, fix all other conflicts in the
+  branch, and then run some cargo command (like `cargo tree` or `cargo check`),
+  which should re-update the lockfile with your own local changes. If you previously
+  ran some `cargo update` commands in your branch, you can re-run them that this
+  time. The community has been looking to resolve merge conflicts with `Cargo.lock`
   and `Cargo.toml` using a [custom merge tool].
 
 

src/doc/src/reference/external-tools.md

@@ -205,22 +205,22 @@ may be found in [the chapter on build scripts](build-scripts.md).
     "reason": "build-script-executed",
     /* The Package ID, a unique identifier for referring to the package. */
     "package_id": "my-package 0.1.0 (path+file:///path/to/my-package)",
-    /* Array of libraries to link, as indicated by the `cargo:rustc-link-lib`
+    /* Array of libraries to link, as indicated by the `cargo::rustc-link-lib`
        instruction. Note that this may include a "KIND=" prefix in the string
        where KIND is the library kind.
     */
     "linked_libs": ["foo", "static=bar"],
     /* Array of paths to include in the library search path, as indicated by
-       the `cargo:rustc-link-search` instruction. Note that this may include a
+       the `cargo::rustc-link-search` instruction. Note that this may include a
        "KIND=" prefix in the string where KIND is the library kind.
     */
     "linked_paths": ["/some/path", "native=/another/path"],
-    /* Array of cfg values to enable, as indicated by the `cargo:rustc-cfg`
+    /* Array of cfg values to enable, as indicated by the `cargo::rustc-cfg`
        instruction.
     */
     "cfgs": ["cfg1", "cfg2=\"string\""],
     /* Array of [KEY, VALUE] arrays of environment variables to set, as
-       indicated by the `cargo:rustc-env` instruction.
+       indicated by the `cargo::rustc-env` instruction.
     */
     "env": [
         ["SOME_KEY", "some value"],

src/doc/src/reference/unstable.md

@@ -1095,7 +1095,7 @@ You can use the flag like this:
 cargo check -Z unstable-options -Z check-cfg
 ```
 
-### `cargo:rustc-check-cfg=CHECK_CFG`
+### `cargo::rustc-check-cfg=CHECK_CFG`
 
 The `rustc-check-cfg` instruction tells Cargo to pass the given value to the
 `--check-cfg` flag to the compiler. This may be used for compile-time
@@ -1111,7 +1111,7 @@ You can use the instruction like this:
 
 ```rust,no_run
 // build.rs
-println!("cargo:rustc-check-cfg=cfg(foo, bar)");
+println!("cargo::rustc-check-cfg=cfg(foo, bar)");
 ```
 
 ```

tests/testsuite/check_cfg.rs

@@ -532,15 +532,15 @@ fn build_script_feature_gate() {
         .file(
             "build.rs",
             r#"fn main() {
-                println!("cargo:rustc-check-cfg=cfg(foo)");
-                println!("cargo:rustc-cfg=foo");
+                println!("cargo::rustc-check-cfg=cfg(foo)");
+                println!("cargo::rustc-cfg=foo");
             }"#,
         )
         .file("src/main.rs", "fn main() {}")
         .build();
 
     p.cargo("check")
-        .with_stderr_contains("warning[..]cargo:rustc-check-cfg requires -Zcheck-cfg flag")
+        .with_stderr_contains("warning[..]cargo::rustc-check-cfg requires -Zcheck-cfg flag")
         .with_status(0)
         .run();
 }