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.
This commit is contained in:
@@ -0,0 +1,19 @@
|
||||
# Benchmark
|
||||
|
||||
*Benchmark* is a tool to benchmark some components of Vanetza.
|
||||
At the moment, benchmarks for signing and validating packets exist.
|
||||
|
||||
## Installation
|
||||
|
||||
Benchmarks are not built by default, so you need to enable them explicitly.
|
||||
Run `cmake -D BUILD_BENCHMARK=ON ..` in your build directory to do so and start the build process again.
|
||||
You should be able to find `bin/benchmark` in your build directory afterwards.
|
||||
|
||||
## Running
|
||||
|
||||
You can run `bin/benchmark --help` to get a list of available benchmarks.
|
||||
You can run these with `bin/benchmark <name>` then.
|
||||
|
||||
## Acknowledgement
|
||||
|
||||
This application has been initially developed [Niklas Keller](https://github.com/kelunik).
|
||||
Reference in New Issue
Block a user