From 35e3dcd83b4e4db8bb38020d1db8a1f1f34230cb Mon Sep 17 00:00:00 2001 From: Peter Barker Date: Sun, 19 Mar 2023 20:26:16 +1100 Subject: [PATCH] AP_RCProtocol: HAL_LOGGING_ENABLED in place of checking build types We don't care how logging works, just that it does --- libraries/AP_RCProtocol/AP_RCProtocol_Backend.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/libraries/AP_RCProtocol/AP_RCProtocol_Backend.cpp b/libraries/AP_RCProtocol/AP_RCProtocol_Backend.cpp index 3459f1748f..024a64ff99 100644 --- a/libraries/AP_RCProtocol/AP_RCProtocol_Backend.cpp +++ b/libraries/AP_RCProtocol/AP_RCProtocol_Backend.cpp @@ -110,7 +110,7 @@ void AP_RCProtocol_Backend::decode_11bit_channels(const uint8_t* data, uint8_t n */ void AP_RCProtocol_Backend::log_data(AP_RCProtocol::rcprotocol_t prot, uint32_t timestamp, const uint8_t *data, uint8_t len) const { -#if !APM_BUILD_TYPE(APM_BUILD_iofirmware) && !APM_BUILD_TYPE(APM_BUILD_UNKNOWN) +#if HAL_LOGGING_ENABLED if (rc().log_raw_data()) { uint32_t u32[10] {}; if (len > sizeof(u32)) { @@ -141,5 +141,5 @@ void AP_RCProtocol_Backend::log_data(AP_RCProtocol::rcprotocol_t prot, uint32_t u32[0], u32[1], u32[2], u32[3], u32[4], u32[5], u32[6], u32[7], u32[8], u32[9]); } -#endif +#endif // HAL_LOGGING_ENABLED }