It's necessary to include QOBject to inherit
Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>

Ability to expose MAVLink enums to QMl

Ready To Fly support based on MAV_SYS_STATUS_PREARM_CHECK

New standalone mission editor unit test

Support for Vehicle and Firmware classes

Upload pre-check must be vehicle-class based

Component Information FTP download support

More work on vehicle connect state machine(s)

Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>

MSVC warns about not identified pragmas
Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>

mavlink as submodule contains more warnings than particles in the universe.
This results in a terrible experience for developers, since it makes harder to find
real warning messages for QGC.
Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>

Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>

This is the Pixhawk research board, not the PX4 production board.

Erros casused by all of the mergedd branches are now fixed for qgroundcontrol.pro. Working on fixing the errors that now appeare in qgcunittest.pro.

qgcunittest.pro now compiles and runs as long as run in terminal in projcts->Run Settings is unchecked.

Replaced the autopilot-specific inclusion of MAVLink to be more generic. Now if you have no actual QGC modifications to make and just want your messages to be available for viewing/logging you can just create the user_config.pri file and override MAVLINK_CONF.