C/C++/Rust

Last validated: 2026-05-05

Oden plugins can be built from native code. The current recommended documentation path should be Rust-first, with C/C++ available for integrations that need it.

Rust

Prefer Rust for new plugins when possible. Rust gives better type safety for Oden data structures and is a good fit for vehicle/control integrations that already use Rust.

Voysys should publish the Rust plugin API docs from the Oden repository and link them here.

C and C++

Use C or C++ when:

  • Existing customer code is already in C/C++.

  • The integration depends on a vendor SDK that is C/C++ only.

  • The plugin must share ABI-level structures with another native component.

Keep C/C++ plugin boundaries small and test dependency loading on the exact deployment image.

What to publish

The public Plugin API section should eventually include:

  • Rust crate API documentation.

  • Minimal plugin template.

  • Global plugin example.

  • Custom entity example.

  • Plugin video capture example.

  • OCP/shared-data example.

  • Packaging and versioning guidance.