Ashin Walpola
d107534eb2
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.
28 lines
691 B
C++
28 lines
691 B
C++
#ifndef TIME_TRIGGER_HPP_XRPGDYXO
|
|
#define TIME_TRIGGER_HPP_XRPGDYXO
|
|
|
|
#include <vanetza/common/manual_runtime.hpp>
|
|
#include <boost/asio/io_context.hpp>
|
|
#include <boost/asio/steady_timer.hpp>
|
|
#include <boost/date_time/posix_time/posix_time_types.hpp>
|
|
|
|
class TimeTrigger
|
|
{
|
|
public:
|
|
TimeTrigger(boost::asio::io_context&);
|
|
vanetza::Runtime& runtime() { return runtime_; }
|
|
void schedule();
|
|
|
|
private:
|
|
boost::posix_time::ptime now() const;
|
|
void on_timeout(const boost::system::error_code&);
|
|
void update_runtime();
|
|
|
|
boost::asio::io_context& io_context_;
|
|
boost::asio::steady_timer timer_;
|
|
vanetza::ManualRuntime runtime_;
|
|
};
|
|
|
|
#endif /* TIME_TRIGGER_HPP_XRPGDYXO */
|
|
|