| commit | 02cae20dd778dde8ce757252f49fff754294f837 | [log] [tgz] |
|---|---|---|
| author | David Tolnay <dtolnay@gmail.com> | Fri Sep 25 21:45:57 2020 |
| committer | GitHub <noreply@github.com> | Fri Sep 25 21:45:57 2020 |
| tree | c7617667e0cbc4626da5b7b0a7a70e3fa7a01bf3 | |
| parent | 58f4f40f93d286c392f12c7b92cf6763b3457b72 [diff] | |
| parent | 37fb86a4aab598a77fd3e81fb2afb2de0eed3927 [diff] |
Merge pull request #4 from dtolnay/plusplus Rename Cargo features to libstdc++ and libc++
-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:
[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"] }