Files
MicrOBU/obu-firmware/external/vanetza-idf/docs/idf/evidence/btp-host-08/adapter-build.json
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

8 lines
476 B
JSON

{
"adapter_sha256": "091929148ecd8866d9a561fb41d7f7426a0db22cc4f81f397cf94cc76dee3ce3",
"binary_sha256": "253600e26949f935113a0c122d0f05ab04876fae96b1711d3be28e96bbc0a6a1",
"testcase_object_sha256": "e506d7762f0ce795943360eb5d685413aa70ae2059981d8b2949a30d3d32dd2d",
"testcase_source_sha256": "764fac9ba93c71ea8b6017f650242b1844d0c661cb058fbd7efa8b6b1f64e08b",
"scope": "Official BTP testcase objects; custom host/device SUT ports; no conformance verdict implied"
}