|author||Zach Johnson <firstname.lastname@example.org>||Tue Nov 17 20:41:48 2020 +0000|
|committer||Automerger Merge Worker <email@example.com>||Tue Nov 17 20:41:48 2020 +0000|
Allow android compiled binaries to use timerfd am: 324882d3be Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/nix/+/1502092 Change-Id: I6006b8c8ba1c9fda4ed4534b5a403640e3344300
Nix seeks to provide friendly bindings to various *nix platform APIs (Linux, Darwin, ...). The goal is to not provide a 100% unified interface, but to unify what can be while still providing platform specific APIs.
For many system APIs, Nix provides a safe alternative to the unsafe APIs exposed by the libc crate. This is done by wrapping the libc functionality with types/abstractions that enforce legal/safe usage.
As an example of what Nix provides, examine the differences between what is exposed by libc and nix for the gethostname system call:
// libc api (unsafe, requires handling return code/errno) pub unsafe extern fn gethostname(name: *mut c_char, len: size_t) -> c_int; // nix api (returns a nix::Result<CStr>) pub fn gethostname<'a>(buffer: &'a mut [u8]) -> Result<&'a CStr>;
nix target support consists of two tiers. While nix attempts to support all platforms supported by libc, only some platforms are actively supported due to either technical or manpower limitations. Support for platforms is split into three tiers:
The following targets are supported by
nix requires Rust 1.36.0 or newer.
nix, add this to your
[dependencies] nix = "0.19.0"
Contributions are very welcome. Please See CONTRIBUTING for additional details.
Feel free to join us in the nix-rust/nix channel on Gitter to discuss
Nix is licensed under the MIT license. See LICENSE for more details.