tag | 8c8cb86f13e2bc3cc17d3f0fd4bb7531e042aac4 | |
---|---|---|
tagger | David Tolnay <dtolnay@gmail.com> | Sat Jan 25 00:05:30 2020 |
object | 690c615e632d1f3ce5b9408b318b34642cd60e28 |
Release 1.0.1
commit | 690c615e632d1f3ce5b9408b318b34642cd60e28 | [log] [tgz] |
---|---|---|
author | David Tolnay <dtolnay@gmail.com> | Sat Jan 25 00:05:30 2020 |
committer | David Tolnay <dtolnay@gmail.com> | Sat Jan 25 00:05:30 2020 |
tree | c184c5f4bba3777d2fb853cd18f85194e598eb4d | |
parent | b591679fc251f75aa91a20ff4bb0954eda3fedfb [diff] |
Release 1.0.1
-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 = ["libstdcxx"] } # or link-cplusplus = { version = "1.0", features = ["libcxx"] }
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"] }