AP_MSP: guard VTX command handler declarations

The msp_process_*_vtx_config and vtx_should_push_config declarations were
unconditional while their definitions are under AP_MSP_VIDEOTX_ENABLED, so
the vtable referenced undefined symbols on any build with the feature off.
Guard the declarations to match.
This commit is contained in:
Andy Piper
2026-07-29 17:16:29 +10:00
committed by Andrew Tridgell
parent 7927e7d862
commit 7bc19ba04c
+2
View File
@@ -243,12 +243,14 @@ protected:
virtual MSP::MSPCommandResult msp_process_out_esc_sensor_data(MSP::sbuf_t *dst);
virtual MSP::MSPCommandResult msp_process_out_rtc(MSP::sbuf_t *dst);
virtual MSP::MSPCommandResult msp_process_out_rc(MSP::sbuf_t *dst);
#if AP_MSP_VIDEOTX_ENABLED
virtual MSP::MSPCommandResult msp_process_out_vtx_config(MSP::sbuf_t *src, MSP::sbuf_t *dst);
virtual MSP::MSPCommandResult msp_process_in_vtx_config(MSP::sbuf_t *src, MSP::sbuf_t *dst);
virtual MSP::MSPCommandResult msp_process_in_vtxtable_powerlevel(MSP::sbuf_t *src, MSP::sbuf_t *dst);
// true when a VTX config push is due this scheduler tick (push on change,
// then repeat MSP_VTX_CONFIG_PUSH_COUNT times)
bool vtx_should_push_config();
#endif
private:
#if AP_MSP_VIDEOTX_ENABLED