Files
MicrOBU/obu-firmware/external/vanetza-idf/vanetza/geonet/repetition_dispatcher.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

35 lines
734 B
C++

#ifndef REPETITION_DISPATCHER_HPP_GO4BAEVL
#define REPETITION_DISPATCHER_HPP_GO4BAEVL
#include <vanetza/geonet/router.hpp>
#include <boost/variant/static_visitor.hpp>
namespace vanetza
{
namespace geonet
{
class RepetitionDispatcher : public boost::static_visitor<void>
{
public:
RepetitionDispatcher(Router& _router, std::unique_ptr<DownPacket> _payload)
: router(_router), payload(std::move(_payload))
{}
template<class REQUEST>
void operator()(const REQUEST& request)
{
router.request(request, std::move(payload));
}
private:
Router& router;
std::unique_ptr<DownPacket> payload;
};
} // namespace geonet
} // namespace vanetza
#endif /* REPETITION_DISPATCHER_HPP_GO4BAEVL */