Vendor dependencies

Let's see how I like this workflow.

vendor/link-cplusplus/Cargo.toml

@@ -0,0 +1,47 @@
+# THIS FILE IS AUTOMATICALLY GENERATED BY CARGO
+#
+# When uploading crates to the registry Cargo will automatically
+# "normalize" Cargo.toml files for maximal compatibility
+# with all versions of Cargo and also rewrite `path` dependencies
+# to registry (e.g., crates.io) dependencies.
+#
+# If you are reading this file be aware that the original Cargo.toml
+# will likely look very different (and much more reasonable).
+# See Cargo.toml.orig for the original contents.
+
+[package]
+edition = "2018"
+rust-version = "1.34"
+name = "link-cplusplus"
+version = "1.0.8"
+authors = ["David Tolnay <dtolnay@gmail.com>"]
+links = "cplusplus"
+description = "Link libstdc++ or libc++ automatically or manually"
+documentation = "https://docs.rs/link-cplusplus"
+readme = "README.md"
+keywords = [
+    "linkage",
+    "c++",
+]
+categories = [
+    "external-ffi-bindings",
+    "development-tools::ffi",
+    "compilers",
+    "no-std",
+]
+license = "MIT OR Apache-2.0"
+repository = "https://github.com/dtolnay/link-cplusplus"
+
+[package.metadata.docs.rs]
+targets = ["x86_64-unknown-linux-gnu"]
+
+[build-dependencies.cc]
+version = "1.0"
+
+[features]
+default = []
+"libc++" = []
+libcxx = ["libc++"]
+"libstdc++" = []
+libstdcxx = ["libstdc++"]
+nothing = []