| commit | 818fe3d162dcb284611f62b61af261adca7a8fa6 | [log] [tgz] |
|---|---|---|
| author | David Tolnay <dtolnay@gmail.com> | Mon Jan 11 23:58:13 2021 |
| committer | David Tolnay <dtolnay@gmail.com> | Mon Jan 11 23:58:13 2021 |
| tree | 69a74cc498b51154fc77c8b0d9116139944eb896 | |
| parent | 8b9bcdac2051d813d933d53a015efa03b6420931 [diff] |
Release 1.0.5
-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:
neither of which are good experiences.
An application or library that is fine with either of libstdc++ or libc++ being linked, whichever is the platform's default, should use the following in Cargo.toml:
[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"] }
Lastly, make sure to add an explicit extern crate dependency to your crate root, since the link-cplusplus crate will be otherwise unused and its link flags dropped.
// src/lib.rs extern crate link_cplusplus;