Windows Cygwin Toolchain
Last updated
Last updated
The following instructions explain how to set up a (Cygwin-based) PX4 development environment on Windows 10. This environment can be used to build PX4 for:
Pixhawk and other NuttX-based hardware
:::warning This setup is an .
The toolchain was previously recommended, but does not work with PX4 v1.12 and later due to packaging issues. The should be used by preference. :::
Download the latest version of the ready-to-use MSI installer from: or (fast download).
Run it, choose your desired installation location, let it install:
Tick the box at the end of the installation to clone the PX4 repository, build and run simulation with jMAVSim (this simplifies the process to get you started). :::note If you missed this step you will need to . :::
:::warning At time of writing the installer is missing some dependencies (and cannot yet be rebuilt to add them - see ).
To add these yourself:
Browse to the toolchain installation directory (default C:\PX4\)
Run run-console.bat (double click) to start the linux-like Cygwin bash console
Enter the following command in the console:
:::
The toolchain uses a specially configured console window (started by running the run-console.bat script) from which you can call the normal PX4 build commands:
Browse to the toolchain installation directory (default C:\PX4\)
Run run-console.bat (double click) to start the linux-like Cygwin bash console (you must use this console to build PX4).
Clone the PX4 PX4-Autopilot repository from within the console:
:::note Skip this step if you ticked the installer option to clone the PX4 repository, build and run simulation with jMAVSim. Cloning only needs to be done once! :::
You can now use the console/PX4-Autopilot repository to build PX4.
For example, to run JMAVSim:
The console will then display:
Once you have finished setting up the command-line toolchain:
Antivirus and other background file monitoring tools can significantly slow down both installation of the toolchain and PX4 build times.
You may wish to halt them temporarily during builds (at your own risk).
We recommend that you force Unix style LF endings for every repository you're working with using this toolchain (and use an editor which preserves them when saving your changes - e.g. Eclipse or VS Code). Compilation of source files also works with CR+LF endings checked out locally, but there are cases in Cygwin (e.g. execution of shell scripts) that require Unix line endings (otherwise you get errors like $'\r': Command not found.). Luckily git can do this for you when you execute the two commands in the root directory of your repo:
If you work with this toolchain on multiple repositories you can also set these two configurations globally for your machine:
This is not recommended because it may affect any other (unrelated) git use on your Windows machine.
Under Unix there's a flag in the permissions of each file that tells the OS whether or not the file is allowed to be executed. git under Cygwin supports and cares about that bit (even though the Windows NTFS file system does not use it). This often results in git finding "false-positive" differences in permissions. The resulting diff might look like this:
We recommend globally disabling the permission check on Windows to avoid the problem:
For existing repositories that have this problem caused by a local configuration, additionally:
Install the
Continue to the .
