Nuno Marques b439dcebf6 docs(windows): clarify native SITL setup and Windows cross-references ...

dev_env_windows_native.md
- Add a "Choosing the C++ Toolchain" subsection up front naming
  MSVC as the default and MinGW-w64 as the alternative for GCC
  workflows, so the rationale is stated once instead of scattered
  across the build / agent sections.
- Trim the Gazebo / jMAVSim "not supported" admonition to a short
  warning linking down to a new "Running Non-SIH Simulators from
  WSL or a Remote Linux Host" section near the end where the
  longer explanation now lives.
- Drop the obsolete "px4-* client wrappers are not reliably
  functional" caveat and matching Known Limitations bullet —
  every wrapper now works fine from a separate PowerShell window.
- Drop the assumed $env:USERPROFILE\Documents clone path here and
  in the agent section; tell readers to use a directory they have
  rights over (e.g. C:\PX4, C:\opt\Micro-XRCE-DDS-Agent) and
  demote the OneDrive / spaces / MAX_PATH caveats from a warning
  to an info box.
- Flip the "Visual Studio 2022 Build Tools installer runs silently
  for 10-15 min" admonition from warning to info — it's a heads-up,
  not a danger.
- Drop "Git for Windows" from the list of things the setup script
  installs (it has to exist before the script can run); add a
  sentence noting the script leaves any existing Git install alone.
- Remove the inline SIH-airframes table and link to the canonical
  table at sim_sih/index.md#supported-vehicle-types instead, so
  we don't keep two lists in sync when new airframes land.
- Note that the agent build is MSVC-only on Windows; PX4 SITL
  itself still builds fine with MinGW.
- Replace the "do not use pip's ninja" warning with a where.exe-
  based diagnostic plus the actual remediation (uninstall the pip
  ninja, or reorder PATH so the winget install wins).
- Add an info admonition above the ROS 2 section clarifying that
  ROS 2 on Windows is OSRF-community-supported, not a first-class
  PX4 platform, and pointing users who would rather run ROS 2
  under WSL2 at that option.

ros2/multi_vehicle.md, ros2/user_guide.md, sim_jmavsim/multi_vehicle.md
- Reword the Windows-native info boxes ("When using the Windows
  Native Development Environment...") so they don't implicitly
  claim to apply to every Windows setup.
Signed-off-by: Nuno Marques <n.marques21@hotmail.com>

2026-05-21 22:21:51 -07:00

..

index.md

docs(sim): restructure hardware sim pages and add SIH docs

2026-03-31 17:01:10 -06:00

multi_vehicle.md

docs(windows): clarify native SITL setup and Windows cross-references

2026-05-21 22:21:51 -07:00