commit | 3cd893f843f22b77282b106465177e5f8b3f818b | [log] [tgz] |
---|---|---|
author | android-build-team Robot <android-build-team-robot@google.com> | Sat May 29 05:05:58 2021 +0000 |
committer | android-build-team Robot <android-build-team-robot@google.com> | Sat May 29 05:05:58 2021 +0000 |
tree | 869c1f1d36551ec634f68df6cf1f9e1807b2b072 | |
parent | ae1fd01f4d0cb6a33a22a9436236dc1842caf10f [diff] | |
parent | 1f25d89657b678c6bf0da9c778148f0592d9a143 [diff] |
Snap for 7408822 from 1f25d89657b678c6bf0da9c778148f0592d9a143 to tm-release Change-Id: Ic3f48d24b12c24ef99722d155ee6a384dbc67bcd
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
:
Tier 1:
Tier 2:
Tier 3:
nix
requires Rust 1.40.0 or newer.
To use nix
, add this to your Cargo.toml
:
[dependencies] nix = "0.20.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
development.
Nix is licensed under the MIT license. See LICENSE for more details.