tag | bb4cdcec9201b5d948615fe3faa9f866e68ce282 | |
---|---|---|
tagger | David Tolnay <dtolnay@gmail.com> | Fri Jan 24 23:17:08 2020 |
object | d978d982211c003f1179c64fdd7093953f0193fe |
Release 1.0.0
commit | d978d982211c003f1179c64fdd7093953f0193fe | [log] [tgz] |
---|---|---|
author | David Tolnay <dtolnay@gmail.com> | Fri Jan 24 23:17:08 2020 |
committer | David Tolnay <dtolnay@gmail.com> | Fri Jan 24 23:19:07 2020 |
tree | 8bcbb07bf38cb16929ca174d787c0b8c37e4f242 | |
parent | b417ce3fda0f36f8d97bf9fb5b8f24e30ccaa81b [diff] |
Release 1.0.0
-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:
[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"] }