Google Git
Sign in
chromium / external / github.com / dtolnay / link-cplusplus / refs/tags/upstream/1.0.3
tag12de4df3205b3cc7e605a0bc9714d805a933bcdb
taggerDavid Tolnay <dtolnay@gmail.com>Fri Sep 25 21:46:26 2020
object3631bc8c51cb554c6f7fd4287f6ae00feee3d504 
Release 1.0.3
commit3631bc8c51cb554c6f7fd4287f6ae00feee3d504[log] [tgz]
authorDavid Tolnay <dtolnay@gmail.com>Fri Sep 25 21:46:26 2020
committerDavid Tolnay <dtolnay@gmail.com>Fri Sep 25 21:46:26 2020
tree4065df676d75496ceeb147826b0df48ce9038a40
parent02cae20dd778dde8ce757252f49fff754294f837 [diff]
Release 1.0.3
1 file changed
tree: 4065df676d75496ceeb147826b0df48ce9038a40
  1. .github/
  2. .gitignore
  3. Cargo.toml
  4. LICENSE-APACHE
  5. LICENSE-MIT
  6. README.md
  7. build.rs
  8. src/
README.md

-lstdc++ or -lc++

This crate exists for the purpose of passing -lstdc++ or -lc++ to the linker, while making it possible for an application to make that choice on behalf of its library dependencies.

Without this crate, a library would need to:

  • pick one or the other to link, with no way for downstream applications to override the choice;
  • or link neither and require an explicit link flag provided by downstream applications even if they would be fine with a default choice;

neither of which are good experiences.

Options

An application or library that is fine with either of libstdc++ or libc++ being linked, whichever is the platform's default, should use:

[dependencies]
link-cplusplus = "1.0"

An application that wants a particular one or the other linked should use:

[dependencies]
link-cplusplus = { version = "1.0", features = ["libstdc++"] }

# or

link-cplusplus = { version = "1.0", features = ["libc++"] }

An application that wants to handle its own more complicated logic for link flags from its build script can make this crate do nothing by using:

[dependencies]
link-cplusplus = { version = "1.0", features = ["nothing"] }

License