Crates.io | libindigo-sys |
lib.rs | libindigo-sys |
version | |
source | src |
created_at | 2024-11-29 00:25:45.756752 |
updated_at | 2024-11-29 00:25:45.756752 |
description | Rust FFI bindings for the INDIGO system library generated by bindgen. |
homepage | |
repository | https://github.com/chrsoo/libindigo-rs |
max_upload_size | |
id | 1465090 |
Cargo.toml error: | TOML parse error at line 28, column 1 | 28 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
size | 0 |
The libindigo-sys
crate is a bindgen generated FFI for the upstream INDIGO source code in C found on GitHub.
[!CAUTION] Using
libindigo-sys
directly instead of the libindigo API means writing a lot of unsafe Rust code based on C-pointers.
For more information on using the INDIGO system API, please refer to INDIGO For Developers.
The NOTES document contains some raw notes on how to compile and set the development environment for libindigo-sys
. At some point these raw notes should be upgraded to proper documentation.
The libindigo-sys
crate will do one of the following in order of priority when building the crate
Attempt to build INDIGO from the path of the envar INDIGO_SOURCE, if specified.
Attempt to build INDIGO from the path of the git submodule externals/indigo
, if it has been initialised by git.
git submodule update --init --recursive
Use INDIGO system headers in /usr/include
and libs from /usr/lib
, if /usr/include/indigo/indigo_version.h
exists.
Initialise the git externals/indigo
git submodule with the command above and build it.