Skip to content

docs: align toolchain and code style with C++20 library#2923

Merged
julianoes merged 2 commits into
mavlink:mainfrom
Bartok9:aerial/docs-cpp20-toolchain-2026-07-14
Jul 14, 2026
Merged

docs: align toolchain and code style with C++20 library#2923
julianoes merged 2 commits into
mavlink:mainfrom
Bartok9:aerial/docs-cpp20-toolchain-2026-07-14

Conversation

@Bartok9

@Bartok9 Bartok9 commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Document that the MAVSDK core library is C++20 (cpp/src/CMakeLists.txt CMAKE_CXX_STANDARD 20, examples already on 20, repo description “C++ 20”).
  • Update the sample CMakeLists.txt in the toolchain guide to recommend CMAKE_CXX_STANDARD 20.
  • Soft-update code-style guidance so new contributions/examples prefer C++20 while still welcoming clear C++17/STL usage.

Why

Docs still said the core was “written in C++17”, which confuses users trying to match the tree.

Non-overlap

Does not touch the Markdown fixes in open #2922 (that PR covers connections fence, quickstart fence, build paths, etc.).

Test plan

  • Docs-only; no C++/CMake library flag changes
  • Spot-check relative statements against cpp/src/CMakeLists.txt and example CMakeLists

The core library and in-tree examples already set CMAKE_CXX_STANDARD 20
and the GitHub description lists C++20; docs still described a C++17 core.
Comment thread docs/en/cpp/guide/code_style.md Outdated
@Bartok9

Bartok9 commented Jul 14, 2026

Copy link
Copy Markdown
Contributor Author

Thanks @julianoes — good call, that second sentence was muddled. Applied your suggestion (simplified to the single C++20 line) and pushed. Let me know if you'd prefer to drop the STL note entirely.

@julianoes
julianoes merged commit 4831856 into mavlink:main Jul 14, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants