Files
MicrOBU/microbu-esp32c5/external/vanetza-idf/vanetza/rpc/CMakeLists.txt
T
Ashin Walpola 0e9525162d 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).
2026-09-23 17:46:40 +02:00

21 lines
927 B
CMake

if(VANETZA_WITH_RPC)
message(STATUS "Enabled Vanetza RPC feature")
set(CAPNP_VERSION_STAMP "${CMAKE_CURRENT_BINARY_DIR}/capnp_version.stamp")
file(WRITE "${CAPNP_VERSION_STAMP}.tmp" "${CapnProto_VERSION}")
execute_process(COMMAND ${CMAKE_COMMAND} -E copy_if_different
"${CAPNP_VERSION_STAMP}.tmp" "${CAPNP_VERSION_STAMP}")
capnp_generate_cpp(CAPNP_SOURCES CAPNP_HEADERS vanetza.capnp)
add_custom_command(OUTPUT ${CAPNP_SOURCES} ${CAPNP_HEADERS}
APPEND DEPENDS "${CAPNP_VERSION_STAMP}")
add_vanetza_component(rpc
asio_event_port.cpp
asio_stream.cpp
link_layer_client.cpp
${CAPNP_SOURCES} ${CAPNP_HEADERS})
target_include_directories(rpc PRIVATE ${CMAKE_CURRENT_BINARY_DIR})
target_link_libraries(rpc PUBLIC dcc)
target_link_libraries(rpc PUBLIC Boost::headers CapnProto::capnp-rpc)
else()
message(STATUS "Disabled Vanetza RPC feature")
endif()