openharmony_ci
90b8832365
README.OpenSource修改 Created-by: dragonswordy Commit-by: ljy9810 Merged-by: openharmony_ci Description: <!-- Thank you for submitting a PR! We have the contribution guide, please read it if you are new here! <https://github.com/rust-lang/libc/blob/main/CONTRIBUTING.md> Please fill out the below template. --> # Description <!-- Add a short description about what this change does --> https://gitcode.com/openharmony/third_party_rust_unicode-ident/issues/3 # Sources <!-- All API changes must have permalinks to headers. Common sources: * Linux uapi https://github.com/torvalds/linux/tree/master/include/uapi * Glibc https://github.com/bminor/glibc * Musl https://github.com/bminor/musl * Apple XNU https://github.com/apple-oss-distributions/xnu * Android https://cs.android.com/android/platform/superproject/main After navigating to the relevant file, click the triple dots and select "copy permalink" if on GitHub, or l-r (links->commit) for the Android source to get a link to the current version of the header. If sources are closed, link to documentation or paste relevant C definitions. --> # Checklist <!-- Please make sure the following has been done before submitting a PR, or mark it as a draft if you are not sure. --> - [ ] Relevant tests in `libc-test/semver` have been updated - [ ] No placeholder or unstable values like `*LAST` or `*MAX` are included (see [#3131](https://github.com/rust-lang/libc/issues/3131)) - [ ] Tested locally (`cd libc-test && cargo test --target mytarget`); especially relevant for platforms that may not be checked in CI <!-- labels: is this PR a breaking change? If not, we can probably get it in a 0.2 release. Just uncomment the following: @rustbot label +stable-nominated --> See merge request: openharmony/third_party_rust_libc!16
libc - Raw FFI bindings to platforms' system libraries
libc provides all of the definitions necessary to easily interoperate with C
code (or "C-like" code) on each of the platforms that Rust supports. This
includes type definitions (e.g. c_int), constants (e.g. EINVAL) as well as
function headers (e.g. malloc).
This crate exports all underlying platform types, functions, and constants under
the crate root, so all items are accessible as libc::foo. The types and values
of all the exported APIs match the platform that libc is compiled for.
Windows API bindings are not included in this crate. If you are looking for WinAPI bindings, consider using crates like windows-sys.
More detailed information about the design of this library can be found in its associated RFC.
v1.0 Roadmap
Currently, libc has two active branches: main for the upcoming v1.0 release,
and libc-0.2 for the currently published version. By default all pull requests
should target main; once reviewed, they can be cherry picked to the libc-0.2
branch if needed.
We will stop making new v0.2 releases once v1.0 is released.
See the section in CONTRIBUTING.md for more details.
Usage
Add the following to your Cargo.toml:
[dependencies]
libc = "0.2"
Features
-
std: by defaultlibclinks to the standard library. Disable this feature to remove this dependency and be able to uselibcin#![no_std]crates. -
extra_traits: allstructs implemented inlibcareCopyandClone. This feature derivesDebug,Eq,Hash, andPartialEq.
The following features are deprecated:
use_std: this is equivalent tostdconst-extern-fn: this is now enabled by defaultalign: this is now enabled by default
Rust version support
The minimum supported Rust toolchain version is currently Rust 1.63.
Increases to the MSRV are allowed to change without a major (i.e. semver- breaking) release in order to avoid a ripple effect in the ecosystem. A policy for when this may change is a work in progress.
libc may continue to compile with Rust versions older than the current MSRV
but this is not guaranteed.
Platform support
You can see the platform(target)-specific docs on docs.rs, select a platform you want to see.
See ci/verify-build.py for
the platforms on which libc is guaranteed to build for each Rust toolchain.
The test-matrix at GitHub Actions and Cirrus CI show the platforms in which
libc tests are run.
License
This project is licensed under either of
at your option.
Contributing
We welcome all people who want to contribute. Please see the contributing instructions for more information.
Contributions in any form (issues, pull requests, etc.) to this project must adhere to Rust's Code of Conduct.
Unless you explicitly state otherwise, any contribution intentionally submitted
for inclusion in libc by you, as defined in the Apache-2.0 license, shall be
dual licensed as above, without any additional terms or conditions.