The previous framing leaned on "MSVC is what CI exercises" as the
reason MSVC is the default, which is circular — CI uses MSVC
because it's the default, not the other way around.
Restate the rationale as what it actually is: MSVC is Microsoft's
native Windows toolchain, ships with the Windows SDK, produces
binaries against the canonical Windows ABI, and is the toolchain
the broader Windows C++ ecosystem (debugger, profilers, libraries)
is built and tested against — so it gives the cleanest native
Windows experience. Demote the CI mention to a single sentence
noting that both MSVC and MinGW are exercised on every PR (so the
CI green covers the alternative too).
Signed-off-by: Nuno Marques <n.marques21@hotmail.com>
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>
Document the native Windows development environment, setup scripts, SITL usage, and related ROS 2 / simulation notes while keeping the existing WSL and Cygwin pages linked clearly.
* mavlink: reassemble GPS_RTCM_DATA before GPS injection
* Apply minor comment requested changes
* Simplification: remove _completed_sequence asymetric protection
* Handle RTCM payload length which is an exact multiple of 180
* update docs
* lib gnss: new GpsRtcmMessageFragmenter to send RTCM via GPS_RTCM_DATA.hpp
* fix clang
* Remove RTCM fragmenter
* update docs
* Compatibility fallback for older QGroundControl builds that omit the final zero-length fragment
* mavlink receiver, remove while loop to avoid dead lock
* docs(update): Subedit
Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
* docs(docs): format
---------
Co-authored-by: jonas <jonas.perolini@rigi.tech>
Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
The line "Priority is assigned automatically during calibration..."
added in #27393 duplicates information already conveyed by the
surrounding paragraph. Hamish flagged the redundancy in code review.
This PR was AI-assisted (Claude Code) and reviewed by a human
before submission.
Co-authored-by: _pmjn_ <pcminh170701@gmail.com>
Update safety.md, peripherals/parachute.md, and releases/main.md to document the extended COM_PARACHUTE parameter and the new configurable in-flight failsafe behaviour.
Hamish Willee
Nuno Marques
PX4BuildBot
Michael Fritsche
Jonas Perolini
Jorge Rios
pmjnt
Alexander Lerach
Claudio Chies
Matthias Grob
gguidone
Julian Oes