Keep the colleague's microbu-esp32c5 tree in this repository

obu-firmware builds against vanetza-idf from microbu-esp32c5/external, but
that tree was gitignored, so a clone of this repository could not build the
firmware it ships. It is now committed here as ordinary files in its own
folder, microbu-esp32c5/: the colleague's commit cf4b99f plus the V2X2MAP
bridge's signature verification (--trust) used on the bench. Nothing is
fetched from or pushed to the colleague's repository; this repository and
its remotes carry everything. The folder's own .gitignore keeps build output,
downloaded components and private key material out, as it did there; the
committed file set is identical to that repository's tracked files.

The ESP32-C5 is still flashed from obu-firmware/, which only takes
vanetza-idf from microbu-esp32c5/, so the two stay separate folders.
FLASHING.md says how to take a newer version of the colleague's tree (copy
it over the folder, rebuild, test, commit).

This commit is contained in:

Ashin Walpola

2026-09-23 17:46:40 +02:00

parent 2f60623e18

commit 0e9525162d

9881 changed files with 1582523 additions and 17 deletions

microbu-esp32c5/external/vanetza-idf/gtest/.gitignore

View File

@@ -0,0 +1,4 @@
 *.zip
 *.tar.gz
 gtest-*/
 googletest-*/

									
										microbu-esp32c5/external/vanetza-idf/gtest/CMakeLists.txt
									
Vendored

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

				include(GoogleTestTargets)

				# export some variables into parent scope

				set(GTest_LIBRARY ${GTest_LIBRARY} PARENT_SCOPE)

				set(GTest_MAIN_LIBRARY ${GTest_MAIN_LIBRARY} PARENT_SCOPE)

				set(GTest_INCLUDE_DIR ${GTest_INCLUDE_DIR} PARENT_SCOPE)