Setting up the waf Build Environment on Windows using Cygwin¶
These setup instructions describe how to setup Cygwin on so that waf (the build system) can run natively on windows and build for all supported boards.
There is a pre-built script at /ardupilot/Tools/environment_install/install-prereqs-windows.ps1 that will automatically perform all of the below steps.
Open a web browser to www.cygwin.com/install.html and download “setup-x86_64.exe”
Paste the following command at a DOS prompt (press window and R key then enter cmd) in the directory where you downloaded “Run setup-x86_64.exe”
setup-x86_64.exe -P autoconf,automake,ccache,cygwin32-gcc-g++,gcc-g++,git,libtool,make,gawk,libexpat-devel,libxml2-devel,python37,python37-future,python37-lxml,python37-pip,libxslt-devel,python37-devel,procps-ng,zip,gdb,ddd
Or, for a stepped install:
Open a web browser to www.cygwin.com/install.html and run setup-x86_64.exe”
Accept the prompts (including default file locations) until you reach the Select Packages dialog.
Select the required packages from the thousands of available packages. Refer to the list below and enter each package “Name” into the Search field as shown below. When you have found the package, click on the Skip button to change it to a version number and then move onto the next package:
Category / Name / Description
Devel | autoconf: Wrapper scripts for autoconf commands
Devel | automake: Wrapper scripts for automake and aclocal
Devel | ccache: A C compiler cache for improving recompilation
Devel | GCC for Cygwin 32bit toolchain (C++)
Devel | gcc-g++ GNU Compiler Collection (C++)
Devel | git: Distributed version control system
Devel | libtool: Generic library support script
Devel | make: The GNU version of the ‘make’ utility
Interpreters | gawk: GNU awk, a pattern scanning and processing language
Libs | libexpat-devel: Expat XML parser library (development files)
Libs | libxml2-devel: Gnome XML library (development)
Libs | libxslt-devel: XML template library (development files)
Python | python37: Python3 language interpreter
Python | python37-devel: Python3 language interpreter
Python | python37-future: Clean single-source support for Python 3 and 2
Python | python37-lxml: Gnome XML Library (Python bindings)
Python | python37-pip: Python package installation tool
System | procps-ng: System and process monitoring utilities (required for pkill)
Devel | gdb: The GNU Debugger
Devel | ddd: DDD, the data display debugger
Archive | zip: Info-ZIP compression utility
When all the packages are selected, click through the rest of the prompts and accept all other default options (including the additional dependencies).
Select Finish to start downloading and installing the packages.
Sometimes the installation can stall because anti-virus protection software is running. If this occurs, shutdown all other programs on your PC including the anti-virus protection, and try again.
Install the GCC compiler¶
This step is only required if you intend to compile for ARM-based boards.
The MAVProxy GCS is required when running SITL. If you’re not planning to run SITL, you can skip this step.
To install MAVProxy on Windows follow the MAVProxy documentation.
Set up directories/paths and extra packages in Cygwin¶
open and then close the “Cygwin Terminal” application from the desktop or start menu icon. This creates initialization files for the user in the Cygwin home directory.
open the “Cygwin Terminal” application from the desktop or start menu icon. Enter the following command to set Python 3.7 to be the default Python and then install additional Python packages:
ln -s /usr/bin/python3.7 /usr/bin/python ln -s /usr/bin/pip3.7 /usr/bin/pip pip install empy pyserial pymavlink
Download ArduPilot Source¶
“Cloning” is git’s term for making a local copy of a remote repository (i.e. one held on the GitHub servers).
Developers should clone the main ArduPilot repository (if they simply want to download and compile the latest code) or their own fork (if they want to make changes to the source code and potentially submit changes back).
Instructions for commonly used tools are below but whichever tool is used, the URL for the source repo will be required. This can be found on the right side of the screen on each Github repository home page but in general the URL is:
https://github.com/ArduPilot/ardupilot.gitfor the main ardupilot repo
https://github.com/your-github-account/ardupilotfor your fork of the ardupilot repo
Cloning with the command line¶
open a terminal and navigate to the directory where you would like the clone to be stored
clone your fork:
git clone https://github.com/your-github-userid/ardupilot cd ardupilot git submodule update --init --recursive
in case some firewalls do not allow ssh access which can cause the above submodule updates to fail, in this instance you can tell git to unilaterally use https through the following command:
git config --global url."https://"
to use https protocols instead of the default git:// prefix.
Build with Waf¶
You should now be able to start the “Cygwin Terminal” application from your Windows Start menu and build with waf as described in BUILD.md.
The build may fail if the file path to some files is too long. If the build fails, please try cloning ArduPilot into a directory very high in the directory structure (i.e. ~/ardupilot).
If during the build process you get an error of missing packet xyz, re-check that you have installed all Cygwin packages listed above
You can run SITL just as you can with any other build environment. To see the terminal, you should install VcXsrv or another X server application for Windows. You must then tell Cygwin where to look for the display by setting the DISPLAY variable.
Build SITL binaries for Windows¶
You can build 32-bit binaries to be run outside of Cygwin with a small set of companion files. This can be useful when used in conjunction with Mission Planner to run SITL with a stable release build rather than a build from the development branch of ArduPilot. This can be done by compiling using the command below in Cygwin and copying the binary the “sitl” folder typically found at C:\Users\user\Documents\Mission Planner\sitl. Mission Planner will download the required files during the first time running SITL. After the initial run, the vehicle-specific binary file can be replaced with the file you built. The custom SITL binaries should be located at /ardupilot/build/sitl.
./waf configure --board=sitl --toolchain i686-pc-cygwin