mirror of
https://github.com/ArduPilot/ardupilot
synced 2025-01-05 15:38:29 -04:00
49314b2b86
Currently installing MAVProxy pulls pymavlink in as a dependency, so we
end up running whatever MAVProxy's master branch is pointing to
(currently pymavlink>=2.3.3).
ardupilot master can reference a pymavlink commit which is not part of
whatever MAVProxy's master branch is pointing to, so we end up with
failures like this in autotest:
fly.ArduCopter:
Mount (Test Camera/Antenna Mount) ('module' object has no attribute 'MAV_CMD_DO_SET_ROI_SYSID') (see /mnt/volume_nyc3_01/autotest/APM/buildlogs/ArduCopter-Mount.txt)
FixedYawCalibration (Test Fixed Yaw Calibration) ('module' object has no attribute 'MAV_CMD_FIXED_MAG_CAL_YAW') (see /mnt/volume_nyc3_01/autotest/APM/buildlogs/ArduCopter-FixedYawCalibration.txt)
If we install pymavlink after installing MAVProxy we should end up with
the pymavlink messages generated from the messages in our mavlink
subdirectory, rather that the pymavlink messages shipped as part of the
pymavlink pip release.
|
||
|---|---|---|
| .. | ||
| AP_Bootloader | ||
| AP_Periph | ||
| ardupilotwaf | ||
| autotest | ||
| bootloaders | ||
| CHDK-Scripts | ||
| CodeStyle | ||
| completion | ||
| CPUInfo | ||
| debug | ||
| environment_install | ||
| FilterTestTool | ||
| Frame_params | ||
| geotag | ||
| GIT_Test | ||
| gittools | ||
| Hello | ||
| IO_Firmware | ||
| Linux_HAL_Essentials | ||
| LogAnalyzer | ||
| mavproxy_modules | ||
| Pozyx/IndoorLoiter | ||
| Replay | ||
| scripts | ||
| UDP_Proxy | ||
| vagrant | ||
| Vicon | ||
| PrintVersion.py | ||