mirror of
https://github.com/PX4/PX4-Autopilot.git
synced 2026-09-25 12:09:56 +08:00
51b9a86a7e
The macOS setup page has not been edited since 2026-04-20, while Tools/setup/macos.sh changed five times after that. The page still describes the px4-sim Homebrew formula, which has been a deprecated no-op in PX4/homebrew-px4 since 2026-04-20, and tells users to add simulation later with `brew install px4-sim`, which installs nothing. On Homebrew 6.0+ it does not even load, because the page never mentions the tap trust the script now performs. Stop enumerating the script's packages and taps in the page; that list is what went stale. Say what the script does in one sentence, point at macos.sh as the source of truth, and document only the user-facing behaviour: Gazebo, XQuartz and a JDK come with --sim-tools, that path needs sudo, taps are trusted for Homebrew 6, and the way to add simulation later is to re-run the script with --sim-tools. Drop the Python prerequisite; the script installs Python and creates the venv itself. Fix the pages it links to that contradict it: the simulation overview still marked Gazebo on Apple Silicon as unstable (pre-dates the 2026-04-20 fix), the supported-targets table claimed Gazebo Classic on macOS with nothing installing it, the jMAVSim page said Java must be installed manually on macOS, and the build troubleshooting page recommended ulimit 300 and running mac_set_ulimit.sh as a script (which cannot change the caller's shell limit). Assisted-by: Claude:claude-fable-5 Signed-off-by: Ramon Roche <mrpollo@gmail.com> Co-authored-by: Farhang <46557204+farhangnaderi@users.noreply.github.com>
36 lines
2.5 KiB
Markdown
36 lines
2.5 KiB
Markdown
# Setting up a Developer Environment (Toolchain)
|
|
|
|
::: tip
|
|
You only need a toolchain if you want to **modify and build** PX4 from source.
|
|
If you just want to run PX4 simulation without changing the code, use a pre-built [Docker container or .deb package](../simulation/px4_sitl_prebuilt_packages.md) instead.
|
|
:::
|
|
|
|
The _supported platforms_ for PX4 development are:
|
|
|
|
- [Ubuntu Linux (24.04/22.04)](../dev_setup/dev_env_linux_ubuntu.md)
|
|
- [Windows (10/11)](../dev_setup/dev_env_windows_wsl.md) — via WSL2
|
|
- [macOS](../dev_setup/dev_env_mac.md)
|
|
|
|
## Supported Targets
|
|
|
|
The table below shows what PX4 targets you can build on each OS.
|
|
|
|
| Target | Linux (Ubuntu) | macOS | Windows |
|
|
| -------------------------------------------------------------------------------------------------------------------------------------- | :------------: | :---: | :-----: |
|
|
| **NuttX based hardware:** [Pixhawk Series](../flight_controller/pixhawk_series.md), [Crazyflie](../complete_vehicles_mc/crazyflie2.md) | ✓ | ✓ | ✓ |
|
|
| **Linux-based hardware:** [Raspberry Pi 2/3](../flight_controller/raspberry_pi_navio2.md) | ✓ | | |
|
|
| **Simulation:** [Gazebo SITL](../sim_gazebo_gz/index.md) | ✓ | ✓ | ✓ |
|
|
| **Simulation:** ROS 2 with Gazebo | ✓ | | ✓ |
|
|
| **Simulation:** [Gazebo Classic SITL](../sim_gazebo_classic/index.md) | | | ✓ |
|
|
| **Simulation:** [ROS with Gazebo Classic](../simulation/ros_interface.md) | | | ✓ |
|
|
|
|
Experienced Docker users can also build with the containers used by our continuous integration system: [Docker Containers](../test_and_ci/docker.md)
|
|
|
|
## Next Steps
|
|
|
|
Once you have finished setting up one of the command-line toolchains above:
|
|
|
|
- Install [VSCode](../dev_setup/vscode.md) (if you prefer using an IDE to the command line).
|
|
- Install the [QGroundControl Daily Build](../dev_setup/qgc_daily_build.md)
|
|
- Continue to [Building PX4 Software](../dev_setup/building_px4.md).
|