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:

Ashin Walpola

2026-09-24 10:56:05 +02:00

parent 2f60623e18

commit d107534eb2

9781 changed files with 1560475 additions and 17 deletions

									
										obu-firmware/external/vanetza-idf/tools/fuzz-harness/fuzz.sh
									
Vendored

		+6
		
												View File
												
				@@ -0,0 +1,6 @@

				#!/bin/bash

				set -eu

				: ${FUZZ_INPUT:="$HOME/input"}

				: ${FUZZ_OUTPUT:="$HOME/output"}

				: ${FUZZ_BUILD:="$HOME/build"}

				afl-fuzz -i $FUZZ_INPUT -o $FUZZ_OUTPUT -c $FUZZ_BUILD/cmplog/bin/fuzzing-persistent -m none -- $FUZZ_BUILD/asan/bin/fuzzing-persistent