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

29 lines
696 B
C++

#ifndef VELOCITY_HPP_0BLFAIDT
#define VELOCITY_HPP_0BLFAIDT
#include <boost/units/quantity.hpp>
#include <boost/units/base_units/metric/knot.hpp>
#include <boost/units/systems/si/velocity.hpp>
namespace vanetza
{
namespace units
{
namespace metric
{
BOOST_UNITS_STATIC_CONSTANT(knot, boost::units::metric::knot_base_unit::unit_type);
BOOST_UNITS_STATIC_CONSTANT(knots, boost::units::metric::knot_base_unit::unit_type);
} // namespace metric
typedef boost::units::quantity<boost::units::si::velocity> Velocity;
typedef boost::units::quantity<boost::units::metric::knot_base_unit::unit_type> NauticalVelocity;
} // namespace units
} // namespace vanetza
#endif /* VELOCITY_HPP_0BLFAIDT */