../../ArduCopter/GCS_Mavlink.cpp: In member function 'void Copter::send_extended_status1(mavlink_channel_t)':
../../ArduCopter/GCS_Mavlink.cpp:281:37: error: suggest parentheses around operand of '!' or change '&' to '&&' or '!' to '~' [-Werror=parentheses]
uint32_t sensors_error_flags = !control_sensors_health & control_sensors_enabled & control_sensors_present;
^
compilation terminated due to -Wfatal-errors.
cc1plus: all warnings being treated as errors
Thanks to Ralph Campbell <ralphcampbell1@gmail.com> for the bug report.
this is for little used options to allow standard firmware builds to
enable those options for development purposes
First option is for MAVLink based ADSB avoidance
Previously a single moment where the vehicle was within 30deg of the target could cause the parachute release counter to reset to zero. This change makes the parachute release if it is spending at least half it's time with more than a 30degree angle error.
That way we avoid recompiling source files that don't depend on vehicles.
Change notes:
- UTILITY_SOURCE_EXTS: moved to ap_library
- Task generators indexes: ap_library handles that now and in a better way
- Use of AP_STLIB_FEATURES: it doesn't make sense anymore, since the stlib
taskgen has empty source list
- Flags and defines: passed down to ap_library through AP_LIBRARIES_OBJECTS_KW
- Set use='mavlink' in AP_LIBRARIES_OBJECTS_KW instead of calls to
bld.ap_stlib().
The functional change here is that we continue to run later checks
when a check fails.
The user-visible effect of that is that your GCS will tell you about
all pre-arm failures, not just the first.
This makes things work a little more like Plane, in preparation for
using AP_Arming.
murata
Jonathan Challinger
Lucas De Marchi
Pierre Kancir
Tom Pittenger
Randy Mackay
Peter Barker
floaledm
John deVere
Andrew Tridgell
Leonard Hall
Michael du Breuil
khancyr
Grant Morphett
Gustavo Jose de Sousa