obu-firmware builds against the vanetza-idf C-ITS library, which until now came from the colleague's microbu-esp32c5 tree beside the repository and was not tracked here, so a clone of this repository could not build the firmware it ships. The library alone is now part of obu-firmware, as obu-firmware/external/vanetza-idf: their external/vanetza-idf at commit cf4b99f, unchanged (9775 files; see its PROVENANCE.md). CMake takes it from there by default; -DVANETZA_IDF_DIR still points the build elsewhere. The rest of the colleague's tree (their own VAM firmware, PKI tooling, station-link Python tools, the V2X2MAP bridge) stays out of this repository and gitignored; nothing is pushed to their repository. NOTES.md, docs/06, TODO.md and the pcap verifier's usage line point at the new location.
40 lines
1.0 KiB
C++
40 lines
1.0 KiB
C++
#ifndef BYTE_BUFFER_SOURCE_HPP_6IBYOI0T
|
|
#define BYTE_BUFFER_SOURCE_HPP_6IBYOI0T
|
|
|
|
#include <vanetza/common/byte_buffer.hpp>
|
|
#include <boost/iostreams/categories.hpp>
|
|
#include <boost/range/iterator_range.hpp>
|
|
|
|
namespace vanetza
|
|
{
|
|
|
|
/**
|
|
* Implementation of boost::iostreams' source device concept.
|
|
* Allows to use a byte buffer as input stream.
|
|
*/
|
|
class byte_buffer_source
|
|
{
|
|
public:
|
|
typedef char char_type;
|
|
typedef boost::iostreams::source_tag category;
|
|
typedef ByteBuffer::const_iterator iterator;
|
|
typedef boost::iterator_range<iterator> range;
|
|
|
|
static_assert(sizeof(char_type) == sizeof(ByteBuffer::value_type),
|
|
"size mismatch of char_type and ByteBuffer::value_type");
|
|
|
|
byte_buffer_source(const ByteBuffer& buffer);
|
|
byte_buffer_source(range r);
|
|
byte_buffer_source(iterator begin, iterator end);
|
|
std::streamsize read(char_type* buf, std::streamsize n);
|
|
|
|
private:
|
|
iterator m_begin;
|
|
iterator m_end;
|
|
};
|
|
|
|
} // namespace vanetza
|
|
|
|
#endif /* BYTE_BUFFER_SOURCE_HPP_6IBYOI0T */
|
|
|