cu-iceoryx2
| Crates.io | cu-iceoryx2 |
| lib.rs | cu-iceoryx2 |
| version | |
| source | src |
| created_at | 2024-11-15 17:46:22.172184 |
| updated_at | 2024-12-05 22:20:09.514676 |
| description | Copper example to use Iceoryx2 as a middleware. |
| homepage | https://github.com/copper-project |
| repository | https://github.com/copper-project/copper-rs |
| max_upload_size | |
| id | 1449377 |
| Cargo.toml error: | TOML parse error at line 18, column 1 | 18 | 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 |
Guillaume Binet (gbin)
documentation
README
cu_iceoryx2
This demonstrates how to use Copper to interface with the Iceoryx2 shared memory communication middleware.
It is useful for Copper users who want to use Iceoryx to communicate with external applications.
You can start the 2 processes in separate terminals:
# Terminal 1
cargo run --bin upstream
# Terminal 2
cargo run --bin downstream
And you should see messages from the caterpillar example (just booleans) getting passed from one copper process to the other.