libftd2xx-ffi
Rust FFI bindings to the FTDI D2XX drivers.
This crate is just the C bindings. There is a separate crate, libftd2xx, which provides safe wrappers around the unsafe C bindings.
Usage
Simply add this crate as a dependency in your Cargo.toml.
The static library is distributed in this crate with permission from FTDI.
[]
= "~0.5.1"
The default feature set will use pre-generated bindings. This is only available for Windows x86_64 and Linux x86_64 platforms.
The bindings can also be generated during compilation using the bindgen feature flag.
[]
= { = "~0.5.1", = ["bindgen"] }
Bindgen has additional dependencies that must be installed in order to compile successfully, see the bindgen requirements page for more details.
Supported Targets
Tested Targets
x86_64-pc-windows-msvc(dynamic linking only)x86_64-unknown-linux-gnu(static linking only)x86_64-unknown-linux-musl(static linking only)
Untested Targets
These targets are provided, but they are untested. Use at your own risk.
aarch64-unknown-linux-gnu(static linking only)aarch64-unknown-linux-musl(static linking only)arm-unknown-linux-gnueabihf(static linking only)arm-unknown-linux-musleabihf(static linking only)armv7-unknown-linux-gnueabihf(static linking only)armv7-unknown-linux-musleabihf(static linking only)i686-pc-windows-msvc(dynamic linking only)i686-unknown-linux-gnu(static linking only)i686-unknown-linux-musl(static linking only)
References
Troubleshooting
Unknown Device on Linux
Remove the VCP FTDI driver.
See FTDI Drivers Installation Guide for Linux for more details.
License
FTDI provides the D2XX driver as a compiled library and a header file.
These files can be found within the vendor directory.
The code within the vendor directory is licensed by FTDI.
Please see the Driver License Terms page for their license.
All code outside of the vendor directory is MIT licensed.
Note: This crate is not affiliated with FTDI. You will need to contact the vendor for any support requests with the underlying library because it is closed source.