tag | 12de4df3205b3cc7e605a0bc9714d805a933bcdb | |
---|---|---|
tagger | David Tolnay <dtolnay@gmail.com> | Fri Sep 25 21:46:26 2020 |
object | 3631bc8c51cb554c6f7fd4287f6ae00feee3d504 |
Release 1.0.3
commit | 3631bc8c51cb554c6f7fd4287f6ae00feee3d504 | [log] [tgz] |
---|---|---|
author | David Tolnay <dtolnay@gmail.com> | Fri Sep 25 21:46:26 2020 |
committer | David Tolnay <dtolnay@gmail.com> | Fri Sep 25 21:46:26 2020 |
tree | 4065df676d75496ceeb147826b0df48ce9038a40 | |
parent | 02cae20dd778dde8ce757252f49fff754294f837 [diff] |
Release 1.0.3
-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 = ["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"] }