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:
+15
@@ -0,0 +1,15 @@
|
||||
{
|
||||
"adapter_sha256": "d31eebbf567be0c2e5d3e9ac7ddf2c4a585bc2a30d939c857e3ae7a4a863fddb",
|
||||
"binary_sha256": "6b77e9371fff7aa171b3fd9efd93ca0f99e6215cca07dc7782426deda3d6b6a7",
|
||||
"testcase_object_sha256": "22768d8957504590104401f742680fc5aa9680ad5062790e0e04f36e6ca44b57",
|
||||
"testcase_source_sha256": "862a7eecc337cefb8d055e558d66f325489e48530f7302bf0f4b948f1d6b16b4",
|
||||
"scope": "Official Security testcase objects; custom host SUT ports for the sending side (GN-MGMT beacons, CAM/DENM carriers); receiving cases not wired; no conformance verdict implied",
|
||||
"suite_overlay": [
|
||||
{
|
||||
"path": "ccsrc/Protocols/GeoNetworking/geonetworking_codec.cc",
|
||||
"before": "a01ee9c560d093f785c2a9fa113dc16a9645e16fa537d1539666642374b635c8",
|
||||
"after": "5bdf56506e59a647d0d321ce768ca1951ba9d119cfcf53da61fa1cc19590ceaa",
|
||||
"reason": "Same null-params guard as the GeoNetworking adapter build; pinned source untouched."
|
||||
}
|
||||
]
|
||||
}
|
||||
Reference in New Issue
Block a user