obu-firmware builds against vanetza-idf from microbu-esp32c5/external, but that tree was gitignored, so a clone of this repository could not build the firmware it ships. It is now committed here as ordinary files in its own folder, microbu-esp32c5/: the colleague's commit cf4b99f plus the V2X2MAP bridge's signature verification (--trust) used on the bench. Nothing is fetched from or pushed to the colleague's repository; this repository and its remotes carry everything. The folder's own .gitignore keeps build output, downloaded components and private key material out, as it did there; the committed file set is identical to that repository's tracked files. The ESP32-C5 is still flashed from obu-firmware/, which only takes vanetza-idf from microbu-esp32c5/, so the two stay separate folders. FLASHING.md says how to take a newer version of the colleague's tree (copy it over the folder, rebuild, test, commit).
29 lines
696 B
C++
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 */
|
|
|