|
|
||
|---|---|---|
| ci | ||
| libc-test | ||
| src | ||
| .gitignore | ||
| .travis.yml | ||
| appveyor.yml | ||
| Cargo.toml | ||
| LICENSE-APACHE | ||
| LICENSE-MIT | ||
| README.md | ||
libc
A Rust library with native bindings to the types and functions commonly found on various systems, including libc.
Usage
First, add the following to your Cargo.toml:
[dependencies]
libc = "0.2"
Next, add this to your crate root:
extern crate libc;
Currently libc by default links to the standard library, but if you would
instead like to use libc in a #![no_std] situation or crate you can request
this via:
[dependencies]
libc = { version = "0.2", default-features = false }
What is libc?
The primary purpose of this crate is to provide 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 does not strive to have any form of compatibility across platforms, but rather it is simply a straight binding to the system libraries on the platform in question.
Public API
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.
More detailed information about the design of this library can be found in its associated RFC.
Adding an API
Want to use an API which currently isn't bound in libc? It's quite easy to add
one!
The internal structure of this crate is designed to minimize the number of
#[cfg] attributes in order to easily be able to add new items which apply
to all platforms in the future. As a result, the crate is organized
hierarchically based on platform. Each module has a number of #[cfg]'d
children, but only one is ever actually compiled. Each module then reexports all
the contents of its children.
This means that for each platform that libc supports, the path from a
leaf module to the root will contain all bindings for the platform in question.
Consequently, this indicates where an API should be added! Adding an API at a
particular level in the hierarchy means that it is supported on all the child
platforms of that level. For example, when adding a Unix API it should be added
to src/unix/mod.rs, but when adding a Linux-only API it should be added to
src/unix/notbsd/linux/mod.rs.
If you're not 100% sure at what level of the hierarchy an API should be added at, fear not! This crate has CI support which tests any binding against all platforms supported, so you'll see failures if an API is added at the wrong level or has different signatures across platforms.
With that in mind, the steps for adding a new API are:
- Determine where in the module hierarchy your API should be added.
- Add the API.
- Send a PR to this repo.
- Wait for CI to pass, fixing errors.
- Wait for a merge!
Platforms and Documentation
The following platforms are currently tested and have documentation available:
Tested:
i686-pc-windows-msvcx86_64-pc-windows-msvc(Windows)i686-pc-windows-gnux86_64-pc-windows-gnui686-apple-darwinx86_64-apple-darwin(OSX)i686-apple-iosx86_64-apple-ios(iOS)i686-unknown-linux-gnux86_64-unknown-linux-gnu(Linux)x86_64-unknown-linux-musl(Linux MUSL)aarch64-unknown-linux-gnumips-unknown-linux-gnuarm-unknown-linux-gnueabihfarm-linux-androideabi(Android)x86_64-unknown-freebsdx86_64-unknown-openbsdx86_64-rumprun-netbsd
The following may be supported, but are not guaranteed to always work:
i686-unknown-freebsdx86_64-unknown-bitrigx86_64-unknown-dragonflyx86_64-unknown-netbsd