Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

add notes on waf build options #6279

Merged
merged 1 commit into from
Sep 17, 2024
Merged

add notes on waf build options #6279

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 21 additions & 1 deletion dev/source/docs/building-setup-linux.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,27 @@ Reload the path (log-out and log-in to make it permanent):

. ~/.profile

Now you should be able to build with waf as described in `BUILD.md <https://github.com/ArduPilot/ardupilot/blob/master/BUILD.md>`__.
Build the code for an autopilot or peripheral board
---------------------------------------------------

Now you should be able to build with waf as described in `BUILD.md <https://github.com/ArduPilot/ardupilot/blob/master/BUILD.md>`__. For example, for a Copter build for the MatekH743 board:

::

./waf configure --board MatekH743
./waf copter

The first configure command should be called only once or when you want to change a
configuration option. One configuration often used is the `--board` option to
switch from one board to another one. For example we could switch to
SkyViper GPS drone and build again:

::

./waf configure --board skyviper-v2450
./waf copter

.. note:: the - -help option will list many build options as well as a list of features that can be enabled or disabled, just as in the `Custom Firmware Build Server <https://custom.ardupilot.org/>`__

.. note:: At this point you have already installed the MAVProxy Ground Control Station (MAVProxy GCS) and are also ready to do Software In the Loop (SITL) simulations of the vehicle code. See :ref:`sitl-simulator-software-in-the-loop` and :ref:`setting-up-sitl-on-linux`. You are ready to not only build the code but run your build in the ArduPilot SITL simulator.

Expand Down