The C libffi library provides two main facilities: assembling calls to functions dynamically, and creating closures that can be called as ordinary C functions. This is an undocumented wrapper, generated by bindgen, intended as the basis for higher-level bindings, but you can see the C libffi documentation.
If you clone this repository in order to build the library and you do
not plan to enable the system Cargo feature to build against your
system’s C libffi, then you should do a recursive clone, by default this
library builds C libffi from a Git submodule.
See the libffi crate for a higher-level API.
libffi-sys can either build its own copy of the libffi C library from
github or it can link against your
system’s C libffi. By default it builds its own because many systems
ship with an old C libffi; this requires that you have a working make,
C compiler, automake, autoconf, and texinfo first. If your system libffi
is up-to-date (v3.2.1 as of October 2019), you can instead enable the
system feature flag to use that. If you want this crate to build
a C libffi for you, add
toml
[dependencies]
libffi-sys = "0.8.0"
to your Cargo.toml. If you want to use your system C libffi, then
toml
[dependencies.libffi-sys]
version = "0.8.0"
features = ["system"]
to your Cargo.toml instead.
This crate supports Rust version 1.32 and later.
The message below means that build.rs is trying to build the C libffi in the
libffi submodule, but the submodule isn’t checked out. Either initialize and
update the submodule or enable the system feature flag.
``
error: failed to run custom build command forlibffi-sys v0.7.1-alpha.0 (/Users/tov/projects/libffi-sys-rs)`
Caused by:
process didn't exit successfully: /Users/tov/projects/libffi-sys-rs/target/debug/build/libffi-sys-0fd86a57f553b770/build-script-build (exit code: 101)
--- stderr
sh: autogen.sh: No such file or directory
thread 'main' panicked at 'Generating configure', build.rs:41:5
note: Run with RUST_BACKTRACE=1 environment variable to display a backtrace.
```