# Building the Code

PX4 can be built on the console or in an IDE, for both simulated and hardware targets.

:::note Before following these instructions you must first install the [Developer Toolchain](dev_env) for your host operating system and target hardware. :::

:::tip For solutions to common build problems see [Troubleshooting](#troubleshooting) below. :::

## Download the PX4 Source Code

The PX4 source code is stored on Github in the [PX4/PX4-Autopilot](https://github.com/PX4/PX4-Autopilot) repository.

To get the _very latest_ ("main") version onto your computer, enter the following command into a terminal:

```sh
git clone https://github.com/PX4/PX4-Autopilot.git --recursive
```

:::note This is all you need to do just to build the latest code. If needed you can also [get the source code specific to a particular release](../../../contribute/code/git_examples#get-a-specific-release). [GIT Examples](../../contribute/code/git_examples) provides a lot more information working with releases and contributing to PX4. :::

## First Build (Using the jMAVSim Simulator)

First we'll build a simulated target using a console environment. This allows us to validate the system setup before moving on to real hardware and an IDE.

Navigate into the **PX4-Autopilot** directory and start [jMAVSim](../simulation/jmavsim) using the following command:

```sh
make px4_sitl jmavsim
```

This will bring up the PX4 console below:

![PX4 Console (jMAVSim)](https://4155462212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LArEa7z2SPawfl3HpCD%2Fuploads%2Fgit-blob-302b1e1f1e6efef9ceecc78de6d053b8e703725f%2Fconsole_jmavsim.png?alt=media)

:::note You may need to start _QGroundControl_ before proceeding, as the default PX4 configuration requires a ground control connection before takeoff. This can be [downloaded from here](https://docs.qgroundcontrol.com/master/en/getting_started/download_and_install.html). :::

The drone can be flown by typing:

```sh
pxh> commander takeoff
```

![jMAVSim UI](https://4155462212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LArEa7z2SPawfl3HpCD%2Fuploads%2Fgit-blob-ae0bac5996c903e1f5a030ceea7b3da3be7ea122%2Fjmavsim_first_takeoff.png?alt=media)

The drone can be landed by typing `commander land` and the whole simulation can be stopped by doing **CTRL+C** (or by entering `shutdown`).

Flying the simulation with the ground control station is closer to the real operation of the vehicle. Click on a location in the map while the vehicle is flying (takeoff flight mode) and enable the slider. This will reposition the vehicle.

![QGroundControl GoTo](https://4155462212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LArEa7z2SPawfl3HpCD%2Fuploads%2Fgit-blob-c3e794a8369c4c9835f0eb366a49f4b9ae984f0d%2Fqgc_goto.jpg?alt=media)

:::tip PX4 can be used with a number of other [Simulators](../simulation), including [Gazebo](../simulation/sim_gazebo_gz), [Gazebo Classic](../simulation/sim_gazebo_classic) and [AirSim](../simulation/airsim). These are also started with _make_ - e.g.

```
make px4_sitl gazebo-classic
```

:::

## NuttX / Pixhawk Based Boards

### Building for NuttX

To build for NuttX- or Pixhawk- based boards, navigate into the **PX4-Autopilot** directory and then call `make` with the build target for your board.

For example, to build for [Pixhawk 4](../../drone_parts/flight_controller/autopilot_pixhawk_standard/pixhawk4) hardware you could use the following command:

```sh
cd PX4-Autopilot
make px4_fmu-v5_default
```

A successful run will end with similar output to:

```sh
-- Build files have been written to: /home/youruser/src/PX4-Autopilot/build/px4_fmu-v4_default
[954/954] Creating /home/youruser/src/PX4-Autopilot/build/px4_fmu-v4_default/px4_fmu-v4_default.px4
```

The first part of the build target `px4_fmu-v4` indicates the target flight controller hardware for the firmware. The suffix, in this case `_default`, indicates a firmware _configuration_, such as supporting or omitting particular features.

:::note The `_default` suffix is optional. For example, `make px4_fmu-v5` and `px4_fmu-v5_default` result in the same firmware. :::

The following list shows the build commands for the [Pixhawk standard](../../drone_parts/flight_controller/autopilot_pixhawk_standard) boards:

* [Holybro Pixhawk 6X (FMUv6X)](../../drone_parts/flight_controller/autopilot_pixhawk_standard/pixhawk6x): `make px4_fmu-v6x_default`
* [Holybro Pixhawk 6C (FMUv6C)](../../drone_parts/flight_controller/autopilot_pixhawk_standard/pixhawk6c): `make px4_fmu-v6c_default`
* [Holybro Pixhawk 6C Mini (FMUv6C)](../../drone_parts/flight_controller/autopilot_pixhawk_standard/pixhawk6c_mini): `make px4_fmu-v6c_default`
* [Holybro Pix32 v6 (FMUv6C)](../../drone_parts/flight_controller/autopilot_pixhawk_standard/holybro_pix32_v6): `make px4_fmu-v6c_default`
* [Holybro Pixhawk 5X (FMUv5X)](../../drone_parts/flight_controller/autopilot_pixhawk_standard/pixhawk5x): `make px4_fmu-v5x_default`
* [Pixhawk 4 (FMUv5)](../../drone_parts/flight_controller/autopilot_pixhawk_standard/pixhawk4): `make px4_fmu-v5_default`
* [Pixhawk 4 Mini (FMUv5)](../../drone_parts/flight_controller/autopilot_pixhawk_standard/pixhawk4_mini): `make px4_fmu-v5_default`
* [CUAV V5+ (FMUv5)](../../drone_parts/flight_controller/autopilot_manufacturer_supported/cuav_v5_plus): `make px4_fmu-v5_default`
* [CUAV V5 nano (FMUv5)](../../drone_parts/flight_controller/autopilot_manufacturer_supported/cuav_v5_nano): `make px4_fmu-v5_default`
* [Pixracer (FMUv4)](../../drone_parts/flight_controller/autopilot_pixhawk_standard/pixracer): `make px4_fmu-v4_default`
* [Pixhawk 3 Pro](../../drone_parts/flight_controller/autopilot_pixhawk_standard/pixhawk3_pro): `make px4_fmu-v4pro_default`
* [Pixhawk Mini](../../drone_parts/flight_controller/autopilot_pixhawk_standard/pixhawk_mini): `make px4_fmu-v3_default`
* [Pixhawk 2 (Cube Black) (FMUv3)](../../drone_parts/flight_controller/autopilot_pixhawk_standard/pixhawk-2): `make px4_fmu-v3_default`
* [mRo Pixhawk (FMUv3)](../../drone_parts/flight_controller/autopilot_pixhawk_standard/mro_pixhawk): `make px4_fmu-v3_default` (supports 2MB Flash)
* [Holybro pix32 (FMUv2)](../../drone_parts/flight_controller/autopilot_discontinued/holybro_pix32): `make px4_fmu-v2_default`
* [Pixfalcon (FMUv2)](../../drone_parts/flight_controller/autopilot_discontinued/pixfalcon): `make px4_fmu-v2_default`
* [Dropix (FMUv2)](../../drone_parts/flight_controller/autopilot_discontinued/dropix): `make px4_fmu-v2_default`
*   [Pixhawk 1 (FMUv2)](../../drone_parts/flight_controller/autopilot_discontinued/pixhawk): `make px4_fmu-v2_default`

    :::warning You **must** use a supported version of GCC to build this board (e.g. the same as used by [CI/docker](../test_and_ci/docker)) or remove modules from the build. Building with an unsupported GCC may fail, as PX4 is close to the board's 1MB flash limit. :::
* Pixhawk 1 with 2 MB flash: `make px4_fmu-v3_default`

Build commands for non-Pixhawk NuttX fight controllers (and for all other-boards) are provided in the documentation for the individual [flight controller boards](../../drone_parts/flight_controller).

### Uploading Firmware (Flashing the board)

Append `upload` to the make commands to upload the compiled binary to the autopilot hardware via USB. For example

```sh
make px4_fmu-v4_default upload
```

A successful run will end with this output:

```sh
Erase  : [====================] 100.0%
Program: [====================] 100.0%
Verify : [====================] 100.0%
Rebooting.

[100%] Built target upload
```

## Other Boards

Build commands for other boards are given the [board-specific flight controller pages](../../drone_parts/flight_controller) (usually under a heading _Building Firmware_).

You can also list all configuration targets using the command:

```sh
make list_config_targets
```

## Compiling in a Graphical IDE

[VSCode](dev_env/vscode) is the officially supported (and recommended) IDE for PX4 development. It is easy to set up and can be used to compile PX4 for both simulation and hardware environments.

## Troubleshooting

### General Build Errors

Many build problems are caused by either mismatching submodules or an incompletely cleaned-up build environment. Updating the submodules and doing a `distclean` can fix these kinds of errors:

```
git submodule update --recursive
make distclean
```

### Flash overflowed by XXX bytes

The `region 'flash' overflowed by XXXX bytes` error indicates that the firmware is too large for the target hardware platform. This is common for `make px4_fmu-v2_default` builds, where the flash size is limited to 1MB.

If you're building the _vanilla_ master branch, the most likely cause is using an unsupported version of GCC. In this case, install the version specified in the [Developer Toolchain](dev_env) instructions.

If building your own branch, it is possibly you have increased the firmware size over the 1MB limit. In this case you will need to remove any drivers/modules that you don't need from the build.

### macOS: Too many open files error

MacOS allows a default maximum of 256 open files in all running processes. The PX4 build system opens a large number of files, so you may exceed this number.

The build toolchain will then report `Too many open files` for many files, as shown below:

```sh
/usr/local/Cellar/gcc-arm-none-eabi/20171218/bin/../lib/gcc/arm-none-eabi/7.2.1/../../../../arm-none-eabi/bin/ld: cannot find NuttX/nuttx/fs/libfs.a: Too many open files
```

The solution is to increase the maximum allowed number of open files (e.g. to 300). You can do this in the macOS _Terminal_ for each session:

* Run this script [Tools/mac\_set\_ulimit.sh](https://github.com/PX4/PX4-Autopilot/blob/main/Tools/mac_set_ulimit.sh), or
*   Enter this command:

    ```sh
    ulimit -S -n 300
    ```

### macOS Catalina: Problem running cmake

As of macOS Catalina 10.15.1 there may be problems when trying to build the simulator with _cmake_. If you have build problems on this platform then try run the following command in your terminal:

```sh
xcode-select --install
sudo ln -s /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/* /usr/local/include/
```

### Ubuntu 18.04: Compile errors involving arm\_none\_eabi\_gcc

Build issues related to `arm_none_eabi_gcc`may be due to a broken g++ toolchain installation. You can verify that this is the case by checking for missing dependencies using:

```bash
arm-none-eabi-gcc --version
arm-none-eabi-g++ --version
arm-none-eabi-gdb --version
arm-none-eabi-size --version
```

Example of bash output with missing dependencies:

```bash
arm-none-eabi-gdb --version
arm-none-eabi-gdb: command not found
```

This can be resolved by removing and [reinstalling the compiler](https://askubuntu.com/questions/1243252/how-to-install-arm-none-eabi-gdb-on-ubuntu-20-04-lts-focal-fossa).

### Ubuntu 18.04: Visual Studio Code is unable to watch for file changes in this large workspace

See [Visual Studio Code IDE (VSCode) > Troubleshooting](../dev_env/vscode#troubleshooting).

### Failed to import Python packages

"Failed to import" errors when running the `make px4_sitl jmavsim` command indicates that some Python packages are not installed (where expected).

```
Failed to import jinja2: No module named 'jinja2'
You may need to install it using:
    pip3 install --user jinja2
```

If you have already installed these dependencies this may be because there is more than one Python version on the computer (e.g. Python 2.7.16 Python 3.8.3), and the module is not present in the version used by the build toolchain.

You should be able to fix this by explicitly installing the dependencies as shown:

```
pip3 install --user pyserial empty toml numpy pandas jinja2 pyyaml pyros-genmsg packaging
```

## PX4 Make Build Targets

The previous sections showed how you can call _make_ to build a number of different targets, start simulators, use IDEs etc. This section shows how _make_ options are constructed and how to find the available choices.

The full syntax to call _make_ with a particular configuration and initialization file is:

```sh
make [VENDOR_][MODEL][_VARIANT] [VIEWER_MODEL_DEBUGGER_WORLD]
```

**VENDOR\_MODEL\_VARIANT**: (also known as `CONFIGURATION_TARGET`)

* **VENDOR:** The manufacturer of the board: `px4`, `aerotenna`, `airmind`, `atlflight`, `auav`, `beaglebone`, `intel`, `nxp`, etc. The vendor name for Pixhawk series boards is `px4`.
* **MODEL:** The _board model_ "model": `sitl`, `fmu-v2`, `fmu-v3`, `fmu-v4`, `fmu-v5`, `navio2`, etc.
* **VARIANT:** Indicates particular configurations: e.g. `bootloader`, `cyphal`, which contain components that are not present in the `default` configuration. Most commonly this is `default`, and may be omitted.

:::tip You can get a list of _all_ available `CONFIGURATION_TARGET` options using the command below:

```sh
make list_config_targets
```

:::

**VIEWER\_MODEL\_DEBUGGER\_WORLD:**

*   **VIEWER:** This is the simulator ("viewer") to launch and connect: `gz`, `gazebo`, `jmavsim`, `none`

    :::tip `none` can be used if you want to launch PX4 and wait for a simulator (jmavsim, Gazebo, Gazebo Classic, or some other simulator). For example, `make px4_sitl none_iris` launches PX4 without a simulator (but with the iris airframe). :::
* **MODEL:** The _vehicle_ model to use (e.g. `iris` (_default_), `rover`, `tailsitter`, etc), which will be loaded by the simulator. The environment variable `PX4_SIM_MODEL` will be set to the selected model, which is then used in the [startup script](../../simulation#startup-scripts) to select appropriate parameters.
* **DEBUGGER:** Debugger to use: `none` (_default_), `ide`, `gdb`, `lldb`, `ddd`, `valgrind`, `callgrind`. For more information see [Simulation Debugging](../debug/simulation_debugging).
* **WORLD:** (Gazebo Classic only). Set the world ([PX4-Autopilot/Tools/simulation/gazebo/sitl\_gazebo/worlds](https://github.com/PX4/PX4-SITL_gazebo/tree/main/worlds)) that is loaded. Default is [empty.world](https://github.com/PX4/PX4-SITL_gazebo/blob/main/worlds/empty.world). For more information see [Gazebo Classic > Loading a Specific World](../../simulation/sim_gazebo_classic#set_world).

:::tip You can get a list of _all_ available `VIEWER_MODEL_DEBUGGER_WORLD` options using the command below:

```sh
make px4_sitl list_vmd_make_targets
```

:::

Notes:

* Most of the values in the `CONFIGURATION_TARGET` and `VIEWER_MODEL_DEBUGGER` have defaults, and are hence optional. For example, `gazebo-classic` is equivalent to `gazebo-classic_iris` or `gazebo-classic_iris_none`.
* You can use three underscores if you want to specify a default value between two other settings. For example, `gazebo-classic___gdb` is equivalent to `gazebo-classic_iris_gdb`.
* You can use a `none` value for `VIEWER_MODEL_DEBUGGER` to start PX4 and wait for a simulator. For example start PX4 using `make px4_sitl_default none` and jMAVSim using `./Tools/simulation/jmavsim/jmavsim_run.sh -l`.

The `VENDOR_MODEL_VARIANT` options map to particular _px4board_ configuration files in the PX4 source tree under the [/boards](https://github.com/PX4/PX4-Autopilot/tree/main/boards) directory. Specifically `VENDOR_MODEL_VARIANT` maps to a configuration file **boards/VENDOR/MODEL/VARIANT.px4board** (e.g. `px4_fmu-v5_default` corresponds to [boards/px4/fmu-v5/default.px4board](https://github.com/PX4/PX4-Autopilot/blob/main/boards/px4/fmu-v5/default.px4board)).

Additional make targets are discussed in relevant sections:

* `bloaty_compare_master`: [Binary Size Profiling](building_px4)
* ...

## Firmware Version & Git Tags

The _PX4 Firmware Version_ and _Custom Firmware Version_ are published using the MAVLink [AUTOPILOT\_VERSION](https://mavlink.io/en/messages/common.html#AUTOPILOT_VERSION) message, and displayed in the _QGroundControl_ **Setup > Summary** airframe panel:

![Firmware info](https://4155462212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LArEa7z2SPawfl3HpCD%2Fuploads%2Fgit-blob-4c05923c6632363115bdd076b2b43ea281dd7d13%2Fqgc_setup_summary_airframe_firmware.jpg?alt=media)

These are extracted at build time from the active _git tag_ for your repo tree. The git tag should be formatted as `<PX4-version>-<vendor-version>` (e.g. the tag in the image above was set to `v1.8.1-2.22.1`).

:::warning If you use a different git tag format, versions information may not be displayed properly. :::
