Ashin Walpola
0e9525162d
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).
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()
|