Files
MicrOBU/obu-firmware/external/vanetza-idf/vanetza/common/byte_sequence.hpp
T
Ashin Walpola d107534eb2 Keep vanetza-idf in obu-firmware, so a plain clone builds the firmware
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.
2026-09-24 10:56:05 +02:00

28 lines
658 B
C++

#ifndef BYTE_SEQUENCE_HPP_10RLFUNF
#define BYTE_SEQUENCE_HPP_10RLFUNF
#include <vanetza/common/byte_buffer.hpp>
#include <functional>
namespace vanetza
{
/**
* Create a random sequence of bytes
* \param length Length of generated byte buffer
* \param seed initializing random number generator
*/
ByteBuffer random_byte_sequence(std::size_t length, int seed = 0);
/**
* Create generator function for random bytes
* \param seed initializing random number generator
* \return Generator function producing random bytes
*/
std::function<uint8_t()> random_byte_generator(int seed = 0);
} // namespace vanetza
#endif /* BYTE_SEQUENCE_HPP_10RLFUNF */