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.
33 lines
580 B
C++
33 lines
580 B
C++
#ifndef SERIALIZATION_HPP_XBJELAF0
|
|
#define SERIALIZATION_HPP_XBJELAF0
|
|
|
|
#include <vanetza/common/serialization.hpp>
|
|
|
|
namespace vanetza
|
|
{
|
|
namespace geonet
|
|
{
|
|
|
|
using vanetza::InputArchive;
|
|
using vanetza::OutputArchive;
|
|
|
|
template<typename T>
|
|
void serialize(T&& t, OutputArchive& oa)
|
|
{
|
|
using vanetza::serialize;
|
|
serialize(oa, std::forward<T>(t));
|
|
}
|
|
|
|
template<typename T>
|
|
void deserialize(T&& t, InputArchive& ia)
|
|
{
|
|
using vanetza::deserialize;
|
|
deserialize(ia, std::forward<T>(t));
|
|
}
|
|
|
|
} // namespace geonet
|
|
} // namespace vanetza
|
|
|
|
#endif /* SERIALIZATION_HPP_XBJELAF0 */
|
|
|