libcsp-sys 0.1.1

FFI bindings for libcsp
Documentation
  • Coverage
  • 45.36%
    83 out of 183 items documented0 out of 12 items with examples
  • Size
  • Source code size: 70.57 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 4.36 MB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 10s Average build duration of successful builds.
  • all releases: 10s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • Homepage
  • Repository
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • robamu

Crates.io docs.rs

libcsp-sys

This crate provides FFI bindings for the libcsp library.

Generally, you probably do not want to use this library directly and instead use the libcsp Rust crate which provides a safe and ergonomic Rust API. You can find some more high-level information and examples in the main repository.

Compile-time configuration of the libcsp-rust library

The libcsp-rust library requires some compile-time configuration file to be included to work properly. You can see an example version of the file for the workspace here. The user has to provide the path to a directory containing this autoconfig.rs file using the CSP_CONFIG_DIR environmental variable.

It is recommended to read the main workspace README for more information to make the generation and specification of this auto-configuration file as conveniently and easy as possible.

Run unittests

Running unittests required the RUN_TESTS environmental variable to be set to 1. This is because the actual libcsp library might be built and linked in a separate crate, so the linker is not able to process -l csp when running the tests.

You can use

RUN_TESTS=1 cargo test

to run the unittests.