DroneCAN libcanard for Debian ============================== This is DroneCAN's libcanard, implementing the UAVCAN v0 transport protocol. It is not the distinct Cyphal/UAVCAN v1 implementation of the same name. The shared library uses classic CAN, one interface, no transmit deadlines, no tail-array-optimization override and no application allocator semaphore hooks. CANARD_64_BIT follows the native target architecture. The CMake target DroneCAN::canard and pkg-config module libcanard select the matching headers and configuration. For example: cc application.c $(pkg-config --cflags --libs libcanard) CMake consumers use find_package(libcanard CONFIG REQUIRED) and link against DroneCAN::canard. Headers are under /usr/include/dronecan to distinguish this protocol implementation from other CAN libraries. Applications defining a different configuration must compile the development sources in /usr/share/libcanard with the same flags as their application, instead of linking libcanard.so.0. The public structures and some function signatures change with CAN FD, multiple interfaces and deadline support. The source tree contains canard.c, canard.h, canard_internals.h, the C++ wrappers and optional driver sources. Do not use the shared-library pkg-config flags when compiling this custom variant. Upstream examples are in /usr/share/doc/libcanard-dev/examples. Their Makefiles describe source-tree builds and require adaptation to the packaged paths and separately generated DSDL messages. This package was motivated as a dependency of ArduPilot. Its sofware-in-the-loop (SITL) setup's requirements include CAN FD, multiple interfaces, deadlines and application-provided allocator semaphore hooks. The supplied sources match its pinned libcanard core. ArduPilot's build integration still needs to select these packaged sources and its own helper headers; this library package does not modify ArduPilot's Waf files.