mirror of https://github.com/ruvnet/RuView synced 2026-08-11 20:41:44 +00:00

Files

T

ruv e737b1a7bc fix(esp32): correct mqtt component name + %u format casts; add build-verified examples

Building veil_ris_controller/veil_sensing_detector for real against ESP-IDF
v5.4 (esp32s3 target) surfaced two compile bugs, now fixed in both the
firmware/privshield/ and wifi-veil/ copies:
- veil_sensing_detector/CMakeLists.txt: PRIV_REQUIRES esp_mqtt -> mqtt
  (esp_mqtt is not a real ESP-IDF v5.4 component name; the real one is mqtt)
- veil_ris_controller.c / veil_sensing_detector.c: ESP_LOGI("%u", ...) calls
  passed a bare uint32_t; -Werror=format= requires (unsigned) casts

Also adds esp32/examples/ — minimal ESP-IDF apps wrapping each component's
public API, added purely to prove they compile+link on a real toolchain.
Still SYNTHETIC / L0, build-only — never flashed, no hardware exists.

2026-08-09 15:46:39 -02:30

926 B

Raw Blame History

ESP32 build-only examples

STATUS: SYNTHETIC / L0 — build-only, never flashed. These two minimal ESP-IDF apps exist only to prove veil_ris_controller and veil_sensing_detector actually compile and link against a real ESP-IDF toolchain (v5.4, esp32s3 target). Building successfully is not a runtime or on-air claim — see ../README.md.

idf.py set-target esp32s3
idf.py build

Both were built and verified locally against ESP-IDF v5.4 (xtensa-esp32s3-elf, GCC 14.2.0); the resulting .bin/.elf are attached to the GitHub release. Building surfaced two real compile errors in the underlying components, both fixed here:

veil_sensing_detector/CMakeLists.txt declared PRIV_REQUIRES esp_mqtt; the actual ESP-IDF v5.4 component is named mqtt.
Two ESP_LOGI(..., "%u", ...) calls passed a bare uint32_t where the toolchain's -Werror=format= requires an explicit (unsigned) cast.

926 B Raw Blame History

ESP32 build-only examples

926 B

Raw Blame History