Files
MicrOBU/obu-firmware/external/vanetza-idf/vanetza/dcc/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

24 lines
572 B
CMake

set(CXX_SOURCES
burst_budget.cpp
bursty_transmit_rate_control.cpp
channel_load.cpp
flow_control.cpp
fully_meshed_state_machine.cpp
gradual_state_machine.cpp
hooked_channel_probe_processor.cpp
limeric.cpp
limeric_budget.cpp
limeric_transmit_rate_control.cpp
mapping.cpp
single_reactive_transmit_rate_control.cpp
state_machine_budget.cpp
smoothing_channel_probe_processor.cpp
transmission.cpp
)
add_vanetza_component(dcc ${CXX_SOURCES})
target_link_libraries(dcc PUBLIC access net)
add_test_subdirectory(tests)