commit | 77958dee5c5d625e2f02f77aa4e307733c5cc3fe | [log] [tgz] |
---|---|---|
author | Joel Galenson <jgalenson@google.com> | Tue Apr 27 14:47:29 2021 -0700 |
committer | Joel Galenson <jgalenson@google.com> | Tue Apr 27 14:47:29 2021 -0700 |
tree | 1b2c9f243e281f08541d4e109f6c11247e4daaa3 | |
parent | 4727c11bc695609981c8fd333b401660cc55e4dc [diff] |
Generate apex_available from c2a instead of a patch Test: Run c2a Test: Build Change-Id: I863ee09b5afb19efb9aa5b3d9408416a5558210a
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.