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.
18 lines
607 B
C++
18 lines
607 B
C++
#ifndef SECURITY_HPP_FV13ZIYA
|
|
#define SECURITY_HPP_FV13ZIYA
|
|
|
|
#include <vanetza/common/position_provider.hpp>
|
|
#include <vanetza/common/runtime.hpp>
|
|
#include <vanetza/security/security_entity.hpp>
|
|
#include <boost/program_options/options_description.hpp>
|
|
#include <boost/program_options/variables_map.hpp>
|
|
#include <memory>
|
|
|
|
std::unique_ptr<vanetza::security::SecurityEntity>
|
|
create_security_entity(const boost::program_options::variables_map&, const vanetza::Runtime&, vanetza::PositionProvider&);
|
|
|
|
void add_security_options(boost::program_options::options_description&);
|
|
|
|
#endif /* SECURITY_HPP_FV13ZIYA */
|
|
|