| tag | 06657b75bf5110dd6420f1e5b6e842c8ef20750d | |
|---|---|---|
| tagger | David Tolnay <dtolnay@gmail.com> | Mon Jul 03 18:21:52 2023 |
| object | df99d8e8be8f609be7e953fa1bffc3735b401d37 |
Release 1.0.9
| commit | df99d8e8be8f609be7e953fa1bffc3735b401d37 | [log] [tgz] |
|---|---|---|
| author | David Tolnay <dtolnay@gmail.com> | Mon Jul 03 18:21:52 2023 |
| committer | David Tolnay <dtolnay@gmail.com> | Mon Jul 03 18:21:52 2023 |
| tree | 8890d6b3f04e9f1fd0293eec8289d324fcbd5c43 | |
| parent | 12ba40b0c709582d23e9c446055352c973279449 [diff] |
Release 1.0.9
-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;