Go to file
David Tolnay c4d90a1b76
Merge pull request #3 from dtolnay/actions
Enable GitHub Actions
2020-05-02 23:50:04 -07:00
.github/workflows Enable GitHub Actions 2020-05-02 23:38:33 -07:00
src Release 1.0.0 2020-01-24 15:19:07 -08:00
.gitignore Implement build script 2020-01-24 14:41:39 -08:00
.travis.yml Add macos and windows CI builds 2020-01-24 15:35:29 -08:00
build.rs Make mac's ar happy 2020-01-24 15:53:50 -08:00
Cargo.toml Select a single docs.rs build target 2020-03-17 13:23:20 -07:00
LICENSE-APACHE Dual mit OR apache license 2020-01-24 14:39:54 -08:00
LICENSE-MIT Dual mit OR apache license 2020-01-24 14:39:54 -08:00
README.md Release 1.0.0 2020-01-24 15:19:07 -08:00

-lstdc++ or -lc++

Build Status Latest Version Rust Documentation

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:

[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"] }

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.