squiid/rust-libc
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity
Rust libc fork for squiid.
5138 commits 2 branches 0 tags 18 MiB
Rust 98.4%
Shell 0.8%
Dockerfile 0.6%
CSS 0.2%
Find a file
bors 25ea72c5ce Auto merge of #2518 - de-vri-es:move-termios2-to-arch, r=Amanieu 
Move termios2 struct and ioctl constants to linux::arch::*.

When trying to use the newly added ioctls from #2508 I noticed that the `termios2` struct was not defined for musl or uclibc, except interestingly for the hexagon+musl target

However, the `termios2` struct and ioctls are part of the Linux headers, not part of the libc headers. So the libc flavour doesn't matter for these definitions.

This PR moves the definitions to the `linux::arch::*` modules, to make them available for all libc flavours and reduce code duplication as a bonus.
2021-11-06 23:14:27 +00:00
.github sparc64: Update debian image to 11 (2021-10-20) to fix segfault on CI 2021-11-03 16:24:14 +09:00
ci sparc64: Update debian image to 11 (2021-10-20) to fix segfault on CI 2021-11-03 16:24:14 +09:00
libc-test Auto merge of #2517 - devnexen:fbsd_ptrace_requpdate, r=JohnTitor 2021-11-06 22:08:53 +00:00
src Auto merge of #2518 - de-vri-es:move-termios2-to-arch, r=Amanieu 2021-11-06 23:14:27 +00:00
tests Run 'cargo fmt' 2019-10-29 09:51:44 -04:00
.cirrus.yml Use released Rustup 1.24.3 2021-06-09 09:58:09 +09:00
.gitignore Ignore the style executable used for testing 2019-02-02 16:32:00 -08:00
build.rs Use ptr::addr_of when available 2021-11-01 19:58:12 -05:00
Cargo.toml Release 0.2.106 to incorporate build fix for #2484 2021-10-31 01:32:28 +02:00
CONTRIBUTING.md Add section about semver list to contributing guide 2021-03-27 10:27:17 +01:00
LICENSE-APACHE Initial commit 2015-01-13 08:22:00 -08:00
LICENSE-MIT Update license year 2020-04-12 03:13:36 +09:00
README.md Replace all mentions about Pipelines with GHA 2021-01-28 18:29:32 +09:00
rustfmt.toml Relax the line length limit to 100 2021-04-06 09:55:52 +09:00
triagebot.toml Allow contributors to label issues via rustbot 2020-10-16 02:24:57 +09:00

README.md

libc - Raw FFI bindings to platforms' system libraries

GHA Status Cirrus CI Status Latest Version Documentation License

libc provides 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 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.

Usage

Add the following to your Cargo.toml:

[dependencies]
libc = "0.2"

Features

  • std: by default libc links to the standard library. Disable this feature to remove this dependency and be able to use libc in #![no_std] crates.

  • extra_traits: all structs implemented in libc are Copy and Clone. This feature derives Debug, Eq, Hash, and PartialEq.

  • const-extern-fn: Changes some extern fns into const extern fns. This feature requires a nightly rustc.

  • deprecated: use_std is deprecated, and is equivalent to std.

Rust version support

The minimum supported Rust toolchain version is Rust 1.13.0 . APIs requiring newer Rust features are only available on newer Rust toolchains:

Feature Version
union 1.19.0
const mem::size_of 1.24.0
repr(align) 1.25.0
extra_traits 1.25.0
core::ffi::c_void 1.30.0
repr(packed(N)) 1.33.0
cfg(target_vendor) 1.33.0

Platform support

Platform-specific documentation (master branch).

See ci/build.sh for the platforms on which libc is guaranteed to build for each Rust toolchain. The test-matrix at GitHub Actions and Cirrus CI show the platforms in which libc tests are run.

License

This project is licensed under either of

at your option.

Contributing

We welcome all people who want to contribute. Please see the contributing instructions for more information.

Contributions in any form (issues, pull requests, etc.) to this project must adhere to Rust's Code of Conduct.

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in libc by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.