depthai-sys

Crates.iodepthai-sys
lib.rsdepthai-sys
version0.1.2
created_at2026-01-01 20:56:09.829746+00
updated_at2026-01-21 23:31:00.911507+00
descriptionLow-level FFI crate that builds/links Luxonis DepthAI-Core v3 and exposes Rust bindings.
homepagehttps://github.com/groupe-carvi/depthai-rs
repositoryhttps://github.com/groupe-carvi/depthai-rs
max_upload_size
id2017497
size374,415
Metakernel (metakernel)

documentation

https://docs.rs/depthai-sys

README

depthai-sys

Low-level FFI crate for depthai-rs.

This crate is responsible for building/downloading Luxonis DepthAI-Core v3 and generating Rust bindings (via autocxx) plus a small C++ wrapper layer.

Most users should depend on the high-level crate instead:

  • High-level crate: depthai

Links

Documentation builds on docs.rs (no-native)

depthai-sys normally builds or downloads DepthAI-Core (and its dependencies) and links the native libraries. That can be too slow for docs.rs, which is time-limited and often network-restricted.

To keep docs.rs builds reliable, this crate provides a feature flag:

  • no-native: bindings-only mode.

When no-native is enabled (or when DOCS_RS=1 is set by docs.rs):

  • autocxx still runs, and the crate still generates the Rust FFI API.
  • ✅ the generated C++ glue from autocxx is compiled in normal builds.
  • ⚠️ on docs.rs (DOCS_RS=1), the build skips compiling the C++ glue to keep docs builds fast.
  • ❌ DepthAI-Core is not downloaded/built.
  • ❌ the custom wrapper (wrapper/wrapper.cpp) is not compiled.
  • ❌ no native link directives are emitted.

This is sufficient for documentation generation, but it is not a runnable configuration.

To build docs locally in the same mode as docs.rs:

  • cargo doc -p depthai-sys --no-default-features --features no-native
Commit count: 156

cargo fmt