a8b7b9c592
add dirname and basename This PR adds `dirname(3)` and `basename(3)` on the following platforms: * Linux with glibc * Linux with musl * Android * FreeBSD * DragonFlyBSD * NetBSD * OpenBSD * Apple platforms I tested this PR on my host machine (Linux with glibc), and got the following error: ``` RUNNING ALL TESTS bad basename function pointer: rust: 140093945892128 (0x7f6a29e14d20) != c 140093945544944 (0x7f6a29dc00f0) thread 'main' panicked at 'some tests failed', /home/steve/Documents/workspace/libc/target/debug/build/libc-test-592f01d15ee93e7a/out/main.rs:12:21 stack backtrace: 0: std::panicking::begin_panic at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/panicking.rs:616:12 1: main::main at /home/steve/Documents/workspace/libc/target/debug/build/libc-test-592f01d15ee93e7a/out/main.rs:12:21 2: core::ops::function::FnOnce::call_once at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/core/src/ops/function.rs:248:5 note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace. error: test failed, to rerun pass '--test main' ``` The reason for this error probably is that there are two `basename(3)` on Linux with glibc, the POSIX version and the GNU version, and they clash with each other. In C, if one `#include <libgen.h>`, then the POSIX version will be available; If one ` #define _GNU_SOURCE` and `#include <string.h>`, then the GNU one will be used. Can we distinguish them in `libc`? |
||
---|---|---|
.github | ||
ci | ||
libc-test | ||
src | ||
tests | ||
.cirrus.yml | ||
.gitignore | ||
build.rs | ||
Cargo.toml | ||
CONTRIBUTING.md | ||
LICENSE-APACHE | ||
LICENSE-MIT | ||
README.md | ||
rustfmt.toml | ||
triagebot.toml |
libc - Raw FFI bindings to platforms' system libraries
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 defaultlibc
links to the standard library. Disable this feature to remove this dependency and be able to uselibc
in#![no_std]
crates. -
extra_traits
: allstruct
s implemented inlibc
areCopy
andClone
. This feature derivesDebug
,Eq
,Hash
, andPartialEq
. -
const-extern-fn
: Changes someextern fn
s intoconst extern fn
s. If you use Rust >= 1.62, this feature is implicitly enabled. Otherwise it requires a nightly rustc. -
deprecated:
use_std
is deprecated, and is equivalent tostd
.
Rust version support
The minimum supported Rust toolchain version is currently Rust 1.13.0. (libc does not currently have any policy regarding changes to the minimum supported Rust version; such policy is a work in progress.) 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 |
const-extern-fn |
1.62.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.