| tag | c7d62b33a1d6650e7265124493fdafd626f108e0 | |
|---|---|---|
| tagger | David Tolnay <dtolnay@gmail.com> | Sat Nov 13 03:01:33 2021 |
| object | eca862190a184c1654ac03e12a37ed0fe817e164 |
Release 1.0.6
| commit | eca862190a184c1654ac03e12a37ed0fe817e164 | [log] [tgz] |
|---|---|---|
| author | David Tolnay <dtolnay@gmail.com> | Sat Nov 13 03:01:33 2021 |
| committer | David Tolnay <dtolnay@gmail.com> | Sat Nov 13 03:01:33 2021 |
| tree | 2b9acef8d95ba897da91383d34000e4902d8d4f1 | |
| parent | fe984467550a89e17b0a7a469dcc828f9a1085b7 [diff] |
Release 1.0.6
-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;