Ashin Walpola
d107534eb2
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.
28 lines
951 B
CMake
28 lines
951 B
CMake
if(NOT TARGET Boost::program_options)
|
|
message(STATUS "Skip build of certify-pqc because Boost::program_options is unavailable")
|
|
return()
|
|
endif()
|
|
|
|
if(NOT TARGET CryptoPP::CryptoPP)
|
|
message(STATUS "Skip build of certify-pqc because CryptoPP is unavailable")
|
|
return()
|
|
endif()
|
|
|
|
add_executable(certify-pqc
|
|
certificate_builder.cpp
|
|
files.cpp
|
|
main.cpp
|
|
)
|
|
target_include_directories(certify-pqc PRIVATE ${CMAKE_CURRENT_SOURCE_DIR})
|
|
target_link_libraries(certify-pqc PRIVATE Boost::program_options vanetza)
|
|
install(TARGETS certify-pqc RUNTIME DESTINATION ${CMAKE_INSTALL_BINDIR})
|
|
|
|
if(BUILD_TESTS AND TARGET certify)
|
|
add_test(NAME CertifyPqcWorkflow
|
|
COMMAND ${CMAKE_COMMAND}
|
|
-DCERTIFY=$<TARGET_FILE:certify>
|
|
-DCERTIFY_PQC=$<TARGET_FILE:certify-pqc>
|
|
-DWORK_DIRECTORY=${PROJECT_BINARY_DIR}/tests/certify-pqc-workflow
|
|
-P ${CMAKE_CURRENT_SOURCE_DIR}/test_workflow.cmake)
|
|
endif()
|