eclipse-iceoryx/iceoryx2

Brief With the update to Rust 1.99.0 cargo doc creates a warning regarding redundant explicit link target, which is elevated to an error on the CI. Unfortunately, there is no location printed and a quick search did not show up anything suspicious. This is potentially a bug in rustdoc. This is the error message error: redundant explicit link target | = note: when a link's destination is not specified, the label is used to resolve intra-doc links = note: `-D rustdoc::redundant-explicit-links` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(rustdoc::redundant_explicit_links)]` error: redundant explicit link target | = note: when a link's destination is not specified, the label is used to resolve intra-doc links error: could not document `iceoryx2` As a workaround, #![allow(rustdoc::redundant_explicit_links)] was added to the lib.rs of the iceoryx2 crate. Action Items retry with new Rust version try to find the faulty link(s) and f

The C, C++ and Python language bindings seem to miss the APIs for Notifier::for_each_listener Notifier::notify_single_listener Notifier::notify_signel_listener_with_custom_event_id Add those APIs with tests.

Required information Operating system: QNX 8.0 Rust version: 1.90.0 Cargo version: 1.90.0 iceoryx2 version: main branch, version 0.9.3 not affected Detailed log output: error: non-item macro in item position: panic --> .cargo/registry/src/index.crates.io-1949cf8c6b5b557f/libc-0.2.189/src/unix/nto/mod.rs:3019:9 | 3019 | panic!("Unsupported arch"); | ^^^^^^^^^^^^^^^^^^^^^^^^^^ error: could not compile `libc` (lib) due to 1 previous error Observed result or behaviour: Summary: The libc dependency version expects a QNX toolchain based on a more recent Rust version. The Rust version in the script and tutorial is out of date, the platform support of QNX have been restructured in the recent Rust compiler versions (e.g. renamed target triplets). See https://doc.rust-lang.org/rustc/platform-support/nto-qnx.html The build script in https://github.com/eclipse-iceoryx/iceoryx2/blob/4f087f30980bc28fa2acc2952b242d43b0e188f4/internal/scripts/qnx_build_rust_toolchain.sh

Brief Since bindgen complicates cross-compilation, the freebsd platform in iceoryx2-pal-posix shall be ported to the libc crate. Ideally, after the port to the libc crate, the iceoryx2-pal-posix crate can be cross-compiled on Linux for FreeBSD with the following commands rustup target add x86_64-unknown-freebsd cargo build -p iceoryx2-pal-posix --target x86_64-unknown-freebsd Once that works, the iceoryx2 crate itself should also cross-compile cargo build -p iceoryx2 --target x86_64-unknown-freebsd

Brief With Rust 1.98, clippy complained about suspicious runtime symbol definitions in the bindgen generated code for macOS on aarch64. As a quick fix, the suspicious_runtime_symbol_definitions warning is suppressed but this is not a long term solution. Since bindgen also complicates cross-compilation, the macos platform in iceoryx2-pal-posix shall be ported to the libc crate. Ideally, after the port to the libc crate, the iceoryx2-pal-posix crate can be cross-compiled on Linux for macOS with the following commands rustup target add x86_64-apple-darwin cargo build -p iceoryx2-pal-posix --target x86_64-apple-darwin Once that works, the iceoryx2 crate itself should also cross-compile cargo build -p iceoryx2 --target x86_64-apple-darwin Task remove #![allow(suspicious_runtime_symbol_definitions)] from iceoryx2-pal/posix/src/lib.rs for macOS