mirror of
https://github.com/esphome/esphome.git
synced 2026-07-10 08:55:36 +00:00
J. Nick Koston
522395f93b
ESPHome's defines.h unconditionally #defines every feature flag for static analysis, so clang-tidy sees ESPHOME_THREAD_MULTI_ATOMICS even when building wake_esp8266.cpp / wake_rp2040.cpp / wake_generic.cpp. In that mode wake.h picks the std::atomic<uint8_t> extern, and the plain-volatile definitions in those TUs trip a redefinition error. Guard each TU's g_wake_requested with the same ESPHOME_THREAD_MULTI_ATOMICS check wake.h uses. Real builds still pick volatile on every SINGLE platform.
