libindigo-sys 0.3.2+INDIGO.2.0.300

Rust FFI bindings for the INDIGO system library generated by bindgen.
docs.rs failed to build libindigo-sys-0.3.2+INDIGO.2.0.300
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.

libindgo-sys

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.

The libindigo-sys crate will do one of the following in order of priority when building the crate

  1. Attempt to build INDIGO from the path of the envar INDIGO_SOURCE, if specified.

  2. Attempt to build INDIGO from the path of the git submodule externals/indigo, if it has been initialised by git. To initialise the git submodule, execute the following command:

    git submodule update --init --recursive --depth 1

  3. Use INDIGO system headers in /usr/include and libs from /usr/lib, if /usr/include/indigo/indigo_version.h exists.

  4. Initialise the git externals/indigo git submodule with the command above and build it.

Updating the indigo submodule to the latest upstream version

  1. Update the module to the latest version in the local file system

    git submodule update --remote

  2. Build and test the new version

  3. Stage and commit the new version

    git add indigo
git commit -m "updated INDIGO to the latest version"