| tag | 99113e801350f106437039078ef10755539e896c | |
|---|---|---|
| tagger | David Tolnay <dtolnay@gmail.com> | Tue Jun 16 18:31:34 2020 |
| object | 58f4f40f93d286c392f12c7b92cf6763b3457b72 |
Release 1.0.2
| commit | 58f4f40f93d286c392f12c7b92cf6763b3457b72 | [log] [tgz] |
|---|---|---|
| author | David Tolnay <dtolnay@gmail.com> | Tue Jun 16 18:31:34 2020 |
| committer | David Tolnay <dtolnay@gmail.com> | Tue Jun 16 18:31:34 2020 |
| tree | 8ade4b12222c87a46d3bf96239f7513a3fa742e9 | |
| parent | f58d20fee3379aef4fdd1d47a2cc626c6d27591d [diff] |
Release 1.0.2
-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"] }