From version 0.2.0 to 0.3.0 the library had support for being compiled as a static library + automatic generation of C headers, enabling seamless integration with C projects. From 0.4.0 onwards, however, the API changed, including typestatification and (currently ongoing) split message preparation/processing.
While things were being moved around, it made sense to temporarily remove the C API. This issue aims at re-enabling it, so that lakers can also be made available for the embedded C world.
geonnave
commented
5 months ago
From version 0.2.0 to 0.3.0 the library had support for being compiled as a static library + automatic generation of C headers, enabling seamless integration with C projects. From 0.4.0 onwards, however, the API changed, including typestatification and (currently ongoing) split message preparation/processing.
While things were being moved around, it made sense to temporarily remove the C API. This issue aims at re-enabling it, so that
lakerscan also be made available for the embedded C world.