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
parent 2f60623e18
commit d107534eb2
9781 changed files with 1560475 additions and 17 deletions
@@ -0,0 +1,14 @@
+# FindCapnProto.cmake – thin wrapper around the upstream CapnProtoConfig.cmake
+#
+# The upstream CapnProtoTargets.cmake unconditionally calls add_library(... IMPORTED)
+# and will therefore fail on repeated find_package() invocations in the same configure run.
+# This wrapper short-circuits the second call when the targets already exist.
+
+if(NOT TARGET CapnProto::capnp)
+    # Forward to upstream CapnProtoConfig.cmake.
+    # Always QUIET, find_package_handle_standard_args below controls options and output
+    find_package(CapnProto CONFIG QUIET)
+endif()
+
+include(FindPackageHandleStandardArgs)
+find_package_handle_standard_args(CapnProto CONFIG_MODE)