#link #libc #linker #cplusplus

sys link-cplusplus

Link libstdc++ or libc++ automatically or manually

6 stable releases

1.0.5 Jan 11, 2021
1.0.4 Oct 7, 2020
1.0.3 Sep 25, 2020
1.0.2 Jun 16, 2020
1.0.1 Jan 25, 2020
Download history 1546/week @ 2020-10-02 1961/week @ 2020-10-09 1365/week @ 2020-10-16 1789/week @ 2020-10-23 3258/week @ 2020-10-30 2451/week @ 2020-11-06 2520/week @ 2020-11-13 2384/week @ 2020-11-20 2220/week @ 2020-11-27 1970/week @ 2020-12-04 1747/week @ 2020-12-11 1683/week @ 2020-12-18 2059/week @ 2020-12-25 2901/week @ 2021-01-01 1902/week @ 2021-01-08 1187/week @ 2021-01-15

9,186 downloads per month
Used in 20 crates (2 directly)



-lstdc++ or -lc++

github crates.io docs.rs build status

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.


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:

link-cplusplus = "1.0"

An application that wants a particular one or the other linked should use:

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:

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;


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.