commit | 13b94f501b9f4d693f942068a37ca90657227b27 | [log] [tgz] |
---|---|---|
author | wdsgyj <gongbo.guan@momenta.ai> | Sun Sep 25 02:17:51 2022 +0800 |
committer | Jiyong Park <jiyong@google.com> | Thu Dec 01 18:01:37 2022 +0900 |
tree | fc264b5098ebcef848a0e17c1c6fe43dbd45ef46 | |
parent | 0d27ecdb7ab125a53c2b30e44a6e621443f0d092 [diff] |
fix crash on Android platform Bug: 259006275 Test: run AVF tests along with aosp/2299538 which excercises this function. (cherry-picked from 9b232dd5815c9f78d13e061a407468a6fad53142) Change-Id: Ib16ae22086799aebd098074c381a75ac5f46c771
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<OsString>) pub fn gethostname() -> Result<OsString>;
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 is supported on Rust 1.46.0 and higher. Its MSRV will not be changed in the future without bumping the major or minor version.
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.