From 77d55d53c12d77ca828a24a160d112ce37a8ef65 Mon Sep 17 00:00:00 2001 From: Hunter McClelland Date: Thu, 5 Mar 2026 08:56:29 -0500 Subject: [PATCH 1/4] docs: Remove outdated mention of git submodules --- .../en/qgc-dev-guide/getting_started/index.md | 23 ++++--------------- 1 file changed, 5 insertions(+), 18 deletions(-) diff --git a/docs/en/qgc-dev-guide/getting_started/index.md b/docs/en/qgc-dev-guide/getting_started/index.md index 1447849e47ed..afc7d12e72d9 100644 --- a/docs/en/qgc-dev-guide/getting_started/index.md +++ b/docs/en/qgc-dev-guide/getting_started/index.md @@ -17,24 +17,11 @@ Versions are provided for all platforms. Source code for _QGroundControl_ is kept on [GitHub](https://github.com/mavlink/qgroundcontrol). It is [dual-licensed under Apache 2.0 and GPLv3](https://github.com/mavlink/qgroundcontrol/blob/master/.github/COPYING.md). -To get the source files: +To get the source files, clone the repo (or your fork): -1. Clone the repo (or your fork) including submodules: - - ```sh - git clone --recursive -j8 https://github.com/mavlink/qgroundcontrol.git - ``` - -2. Update submodules (required each time you pull new source code): - - ```sh - git submodule update --recursive - ``` - -:::tip -Github source-code zip files cannot be used because these do not contain the appropriate submodule source code. -You must use git! -::: +```sh +git clone -j8 https://github.com/mavlink/qgroundcontrol.git +``` ## Build QGroundControl @@ -131,7 +118,7 @@ When installing, select _Desktop development with C++_ as shown: Example commands to build a default QGC and run it afterwards: -1. Make sure you cloned the repository and updated the submodules before, see chapter _Source Code_ above and switch into the repository folder: +1. Make sure you cloned the repository before, see chapter _Source Code_ above and switch into the repository folder: ```sh cd qgroundcontrol From d0493e10418c923af279d998b1421fec69acd169 Mon Sep 17 00:00:00 2001 From: Hunter McClelland Date: Thu, 5 Mar 2026 11:05:02 -0500 Subject: [PATCH 2/4] docs: Fix a broken link to px4 dev docs --- docs/en/qgc-dev-guide/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/en/qgc-dev-guide/index.md b/docs/en/qgc-dev-guide/index.md index 333551d5e0f6..c05ab78315e8 100644 --- a/docs/en/qgc-dev-guide/index.md +++ b/docs/en/qgc-dev-guide/index.md @@ -48,8 +48,8 @@ The translation projects (and join links) are listed below: The PX4 Developer Guide contains additional information about the (common) docs/translation toolchain: -- [Documentation](https://dev.px4.io/en/contribute/docs.html) -- [Translation](https://dev.px4.io/en/contribute/docs.html) +- [Documentation](https://docs.px4.io/main/en/contribute/docs) +- [Translation](https://docs.px4.io/main/en/contribute/docs.html) ## License From 2dd708f0bb8ffeedec14bc018687f0d92d6cb64b Mon Sep 17 00:00:00 2001 From: Hunter McClelland Date: Thu, 5 Mar 2026 11:15:00 -0500 Subject: [PATCH 3/4] docs: Flagging a use of --recursive not found in docs/en/ --- docs/zh/qgc-dev-guide/getting_started/cent_os.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/zh/qgc-dev-guide/getting_started/cent_os.md b/docs/zh/qgc-dev-guide/getting_started/cent_os.md index c709b04874b6..8496646efef4 100644 --- a/docs/zh/qgc-dev-guide/getting_started/cent_os.md +++ b/docs/zh/qgc-dev-guide/getting_started/cent_os.md @@ -191,7 +191,7 @@ Select the following options and install it under `~/devel/Qt`: ### Clone and Build QGC ``` -git clone --recursive https://github.com/mavlink/qgroundcontrol.git +git clone https://github.com/mavlink/qgroundcontrol.git mkdir build cd build ``` From 880714e44fdb9c9ed8277a84d9a3ec954c6a56ce Mon Sep 17 00:00:00 2001 From: Hunter McClelland Date: Thu, 5 Mar 2026 13:57:32 -0500 Subject: [PATCH 4/4] docs: fix harmless typo --- docs/en/qgc-dev-guide/firmware_plugin.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/qgc-dev-guide/firmware_plugin.md b/docs/en/qgc-dev-guide/firmware_plugin.md index 95d0c3ddc74b..d3d793d5df30 100644 --- a/docs/en/qgc-dev-guide/firmware_plugin.md +++ b/docs/en/qgc-dev-guide/firmware_plugin.md @@ -1,6 +1,6 @@ # Plugin Architecture -Although the MAVLink spec defines a standard communication protocol to communicate with a vehicle. There are many aspects of that spec that are up for interpretation by the firmware developers. Because of this there are many cases where communication with a vehicle running one firmware is be slightly different than communication with a vehicle running a different firmware in order to accomplish the same task. Also each firmware may implement a different subset of the MAVLink command set. +Although the MAVLink spec defines a standard communication protocol to communicate with a vehicle. There are many aspects of that spec that are up for interpretation by the firmware developers. Because of this there are many cases where communication with a vehicle running one firmware is slightly different than communication with a vehicle running a different firmware in order to accomplish the same task. Also each firmware may implement a different subset of the MAVLink command set. Another major issue is that the MAVLink spec does not cover vehicle configuration or a common parameter set. Due to this all code which relates to vehicle setup ends up being firmware specific. Also any code which must refer to a specific parameter is also firmware specific.