|author||Carlos Gomes Martinho <email@example.com>||Mon Apr 20 15:17:29 2020 +0200|
|committer||Jim Schaad <firstname.lastname@example.org>||Tue Apr 21 07:38:45 2020 -0700|
build: do not stop if package is not found
This project is a C implementation of the IETF CBOR Encoded Message Syntax (COSE). COSE has reached RFC status and is now available at RFC 8152.
In addition to the core document the following have also become RFCs:
The project is setup to use two different cryptographic
Go ahead, file issues, make pull requests.
before committing changes, run
The project is setup to build using CMake. The way that the CMake files are setup, it requires that version 3.0 or higher is used.
The project requires the use of cn-cbor(https://github.com/jimsch/cn-cbor) in order to build. While this is based on the original version at (https://github.com/cabo/cn-cbor) there have been several updates to this version which have not been reflected in the base library. The CMake configuration files will automatically pull down the correct version when run.
mkdir build cd build cmake .. cmake --build . # if user wants to install sudo cmake --build . --target install
Consuming via cmake find_package (after installation):
find_package(cose-c REQUIRED) add_executable(mytarget main.cpp) target_link_libraries(mytarget cose-c::cose-c)
Consuming via cmake add_subdirectory (e.g. as a submodule):
add_subdirectory(vendor/cose-c) add_executable(mytarget main.cpp) target_link_libraries(mytarget cose-c::cose-c)
Consuming via conan package: add
cose-c/[>=20200417] to your conanfile.txt
add_executable(mytarget main.cpp) target_link_libraries(mytarget cose-c::cose-c)
The memory model used in this library is a mess. This is in large part because the memory model of cn-cbor is still poorly understood.
There are three different memory models that can be used with cn-cbor and cose-c, at this time only one of them is going to produce good results for long running systems.
The cn-cbor project was built with a specific memory model, but did not limit itself to that memory model when writing the code. It was originally designed for working on small devices that use a block allocator with sub-allocations done from that allocated block. This allows for all of the items allocated in that large block to be freed in a single operation when everything is done.
Build without USE_CONTEXT: This model uses standard calloc/free and suffers from the cn-cbor memory model problems.
Build with USE_CONTEXT and pass in NULL: This model is equivalent to the previous configuration.
Build with USE_CONTEXT and pass in a block allocator: This model works, but requires that you provide the allocator.