Website: http://qgroundcontrol.com
Source code for QGroundControl is kept on GitHub: https://github.com/mavlink/qgroundcontrol.
git clone --recursive https://github.com/mavlink/qgroundcontrol.git
Each time you pull new source to your repository you should run git submodule update
to get the latest submodules as well. Since QGroundControl uses submodules, using the zip file for source download will not work. You must use git.
The source code is dual-licensed under Apache 2.0 and GPLv3.
https://docs.qgroundcontrol.com/en/
QGroundControl builds are supported for OSX, Linux, Windows, iOS and Android. QGroundControl uses Qt as its cross-platform support library and uses QtCreator as its default build environment.
You need to install Qt as described below instead of using pre-built packages from say, a Linux distribution, because QGroundControl needs access to private Qt headers.
chmod +x
. Install to default location for use with ./qgroundcontrol-start.sh. If you install Qt to a non-default location you will need to modify qgroundcontrol-start.sh in order to run downloaded builds.qgroundcontrol.pro
project.A Vagrantfile is provided to build QGroundControl using the Vagrant system. This will produce a native Linux build which can be run in the Vagrant Virtual Machine or on the host machine if it is compatible.
CONFIG+=WarningsAsErrorsOn
will turn all warnings into errors which breaks the build. If you are working on a pull request you plan to submit to github for consideration, you should always run with this setting turned on, since it is required for all pull requests. NOTE: Putting this line into a file called "user_config.pri" in the top-level directory (same directory as qgroundcontrol.pro
) will set this flag on all builds without interfering with the GIT history.build_debug
or build_release
directories. The built executable can be found in the debug
or release
directory.QGroundControl has functionality that is dependent on the operating system and libraries installed by the user. The following sections describe these features, their dependencies, and how to disable/alter them during the build process. These features can be forcibly enabled/disabled by specifying additional values to qmake.
Integration with Opal-RT's RT-LAB simulator can be enabled on Windows by installing RT-LAB 7.2.4. This allows vehicles to be simulated in RT-LAB and communicate directly with QGC on the same computer as if the UAS was actually deployed. This support is enabled by default once the requisite RT-LAB software is installed. Disabling this can be done by adding DEFINES+=DISABLE_RTLAB
to qmake.
QGroundControl can talk to XBee wireless devices using their proprietary protocol directly on Windows and Linux platforms. This support is not necessary if you're not using XBee devices or aren't using their proprietary protocol. On Windows, the necessary dependencies are included in this repository and no additional steps are required. For Linux, change to the libs/thirdParty/libxbee
folder and run make;sudo make install
to install libxbee on your system (uninstalling can be done with a sudo make uninstall
). qmake
will automatically detect the library on Linux, so no other work is necessary.
To disable XBee support you may add DEFINES+=DISABLE_XBEE
to qmake.
Check the Video Streaming directory for further instructions.
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。