Hamish Willee 88d623bedb
Move PX4 Guide source into /docs (#24490)
* Add vitepress tree

* Update existing workflows so they dont trigger on changes in the docs path

* Add nojekyll, package.json, LICENCE etc

* Add crowdin docs upload/download scripts

* Add docs flaw checker workflows

* Used docs prefix for docs workflows

* Crowdin obvious fixes

* ci: docs move to self hosted runner

runs on a beefy server for faster builds

Signed-off-by: Ramon Roche <mrpollo@gmail.com>

* ci: don't run build action for docs or ci changes

Signed-off-by: Ramon Roche <mrpollo@gmail.com>

* ci: update runners

Signed-off-by: Ramon Roche <mrpollo@gmail.com>

* Add docs/en

* Add docs assets and scripts

* Fix up editlinks to point to PX4 sources

* Download just the translations that are supported

* Add translation sources for zh, uk, ko

* Update latest tranlsation and uorb graphs

* update vitepress to latest

---------

Signed-off-by: Ramon Roche <mrpollo@gmail.com>
Co-authored-by: Ramon Roche <mrpollo@gmail.com>
2025-03-13 16:08:27 +11:00

2.2 KiB

Setting up a Developer Environment (Toolchain)

The supported platforms for PX4 development are:

Supported Targets

The table below shows what PX4 targets you can build on each OS.

Target Linux (Ubuntu) Mac Windows
NuttX based hardware: Pixhawk Series, Crazyflie
Linux-based hardware: Raspberry Pi 2/3
Simulation: Gazebo SITL
Simulation: Gazebo Classic SITL
Simulation: ROS with Gazebo Classic
Simulation: ROS 2 with Gazebo

Experienced Docker users can also build with the containers used by our continuous integration system: Docker Containers

Next Steps

Once you have finished setting up one of the command-line toolchains above: