10 stable releases
1.0.9 | Jul 3, 2023 |
---|---|
1.0.8 | Dec 17, 2022 |
1.0.7 | Aug 22, 2022 |
1.0.6 | Nov 13, 2021 |
1.0.1 | Jan 25, 2020 |
#39 in Build Utils
881,297 downloads per month
Used in 407 crates
(28 directly)
9KB
-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:
- pick one or the other to link, with no way for downstream applications to override the choice;
- or link neither and require an explicit link flag provided by downstream applications even if they would be fine with a default choice;
neither of which are good experiences.
Options
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;
License
Licensed under either of Apache License, Version 2.0 or MIT license at your option.Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this project by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.
Dependencies
~225KB