Toolchains

[AlexanderLanin]

🚧 DRAFT

C++

• Current: example repo with llvm toolchain + googletest
• Current: example integrated into template

---

• In progress: gcc toolchain 12.2 with SCORE-wide common compiler flags (open: can modules/targets deviate?), we'll start with -Wall -Wextra -pedantic by @nradakovic

---

• Next: llvm/clang toolchain with common compiler flags (open: can modules/targets deviate?), we'll start with -Wall -Wextra -pedantic. Compiler flags will be stored in tooling repository. *
• Next: IDE support via clangd (LSP)*
• Next: clang-tidy*
• Next: clang-format*

---

• Future: sanitizers (gcc or clang, to be decided)
• Future: coding rules (-> process team)
• Future: QNX/qcc toolchains (8.0 vs 7.X to be clarified), POC for 8.0 in progress by @ltekieli

* by takeover from old solution. Potentially in the future improvement by BMW SW Factory contribution.

Rust

• Is it only FEO? Then we can do it later!
• What exactly would need to be moved to infrastructure? e.g. which tools, settings, etc

Python (is that a "toolchain"??? Or just "tools"?)

• Current: "example" in score repo (incl. ruff format)

---

• Next: ruff linting (hint: consider using old solution)
• Next: pyright linting
• Next: coding rules (already agreed, need to be moved to .rst)

---

• Future: combine all python stuff via a centralized place (assuming we have "enough" users). Potentially like docs().
• Future: potentially yet another code analysis tool: pylint
• Future: figure out how to sync tool configs between repositories (currently configs must be in the git root for IDE support)
• Future: better solution for venv