Files
MicrOBU/obu-firmware/external/vanetza-idf/tools/certify/CMakeLists.txt
T
Ashin Walpola d107534eb2 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

25 lines
692 B
CMake

if(NOT TARGET Boost::program_options)
message(STATUS "Skip build of certify because of missing Boost::program_options dependency")
return()
endif()
if(NOT TARGET CryptoPP::CryptoPP)
message(STATUS "Skip build of certify because of missing CryptoPP dependency")
return()
endif()
add_executable(certify
commands/extract-public-key.cpp
commands/generate-aa.cpp
commands/generate-key.cpp
commands/generate-root.cpp
commands/generate-ticket.cpp
commands/show-certificate.cpp
main.cpp
options.cpp
utils.cpp
)
target_include_directories(certify PRIVATE ${CMAKE_CURRENT_SOURCE_DIR})
target_link_libraries(certify Boost::program_options vanetza)