README.md 1.96 KB
Newer Older
Gus Grubba's avatar
Gus Grubba committed
1 2 3 4
# QGroundControl Ground Control Station

## Custom Build Example

5
To build this sample custom version:
Gus Grubba's avatar
Gus Grubba committed
6

7 8 9 10 11
* Clean you build directory of any previous build
* Rename the directory from `custom-example` to `custom`
* Change to the `custom` directory
* Run `python updateqrc.py`
* Build QGC
Gus Grubba's avatar
Gus Grubba committed
12

13
![Custom Build Screenshot](README.jpg)
Gus Grubba's avatar
Gus Grubba committed
14

15
More details on what a custom build is and how to create your own can be found in the [QGC Dev Guide](https://dev.qgroundcontrol.com/en/custom_build/custom_build.html).
Gus Grubba's avatar
Gus Grubba committed
16

17
The main features of this example:
Gus Grubba's avatar
Gus Grubba committed
18

19 20 21 22 23 24 25
* Assumes an "Off The Shelf" purchased commercial vehicle. This means most vehicle setup is hidden from the user since they should mostly never need to adjust those things. They would be set up correctly by the vehicle producing company prior to sale.
* The above assumption cause the QGC UI to adjust and not show various things. Providing an even simpler experience to the user.
* The full experience continues to be available in "Advanced Mode".
* Brands the build with various custom images and custom color palette which matches corporate branding of the theoretical commercial company this build is for.
* Customizes portions of the interface such as you can see in the above screenshot which shows a custom instrument widget replacing the standard QGC ui.
* It also overrides various QGC Application settings to hide some settings the users shouldn't modify as well as adjusting defaults for others.
* The source code is fully commented to explain what and why it is doing things.
Gus Grubba's avatar
Gus Grubba committed
26

27
> Important Note: This custom build is not automatically built each time regular QGC code changes. This can mean that it may fall out of date with the latest changes in QGC code. This can show up as the `python updateqrc.py` steps failing due to upstream resource changes. Or possibly fail to compile because the plugin mechanism for custom builds has changed. If this happens please notify the QGC devs and they will bring it up to date. Or even better, submit a pull for the fix yourself!