5 releases (1 stable)
|1.0.0||Jan 29, 2021|
|1.0.0-alpha3||May 6, 2020|
|1.0.0-alpha2||Apr 16, 2020|
|0.1.0||Feb 2, 2016|
#164 in Hardware support
762 downloads per month
Used in 9 crates (4 directly)
libftdi1-sys is a crate providing Rust bindings to the C library
This crate requires
libftdi1 version 1.4 (August 2017) or later to be available as a system library
that can be found with
pkg-config (everywhere except windows/MSVC) or
unless you activate the
By default the crate uses pregenerated bindings which should be fine in most cases.
In special cases the bindings can be regenerated using the
Regenerating bindings has an additional requirement that
libclang must be installed and visible on your path. If you are using a
gcc-toolchain and don't want to install the entirity of LLVM just for
libclang, you can use the following procedure (using a Debian-based
ARM system as an example):
sudo apt-get install libclang-dev export LIBCLANG_PATH=/usr/lib/llvm-7/lib export C_INCLUDE_PATH=/usr/lib/gcc/arm-linux-gnueabihf/8/include cargo build
The Minimum Supported Rust Version (MSRV) is stable
1.36 with the
Note that it can be possible to build on lower Rust versions
by downgrading some dependencies.
libusb1-sys: depend on
libusb1-sysand use real
libusbtypes instead of placeholders. This makes it possible to interact directly with the underlying
vendored: build a custom copy of
libftdiinstead of using the system one. Note that this includes LGPL code in your build.
bindgen: Generate bindings to
libftdiat compile time.
This crate is expected to be passively maintained, not actively updated.
That being said, if you want to update binding generation,
you can set the
LIBFTDI1_SYS_DEVEL environment variable with any value
so that an updated binding file is written in
src alongside the original one
enabling you to compare them and copy it over the old one to update.