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
+30
View File
@@ -0,0 +1,30 @@
# Legal Notice
As maintainer of Vanetza, I am responsible for this website's content under German Law.
Following contact details are given to comply with § 5 TMG and § 55 Abs. 2 RStV.
Feel free to send me a postcard if you like Vanetza :-)
## Contact
Raphael Riebl
Bergstraße 9
85129 Unterdolling
Germany
E-mail: raphael@riebl.net
I will not answer support requests via e-mail.
Please open an [issue ticket](https://github.com/riebl/vanetza/issues) instead.
## Privacy Statement
I do not collect, store or process any information about visitors of this website.
Please note that the API documentation generated by Doxygen sets a non-essential cookie storing your preferred width of its navigation's sidebar.
This website is hosted by GitHub.
They likely record some personally identifiable information such as your IP address.
Please refer to [GitHub's privacy statement](https://help.github.com/en/github/site-policy/github-privacy-statement) for details.
Furthermore, web fonts are included via [Google Fonts API](https://fonts.google.com).
Google has added a section to their FAQ about [privacy implications](https://developers.google.com/fonts/faq#what_does_using_the_google_fonts_api_mean_for_the_privacy_of_my_users).