Skip to content

docs: correct the Windows compiler claim in README#4

Merged
justinjoy merged 1 commit into
mainfrom
docs-readme-windows-compiler
Jun 29, 2026
Merged

docs: correct the Windows compiler claim in README#4
justinjoy merged 1 commit into
mainfrom
docs-readme-windows-compiler

Conversation

@justinjoy

Copy link
Copy Markdown
Collaborator

Problem

The build-requirements list claims MSVC >= VS 2019, but that is not
what the project builds or tests. CI never invokes the MSVC cl
compiler — the Windows lane (see ci-pr.yml / ci-main.yml) configures
with clang-cl (clang targeting the MSVC ABI) under the MSVC
toolchain, because the glib dependency is exercised through clang-cl,
not cl. The >= VS 2019 floor is likewise unverified (CI runs on
windows-latest = VS 2022).

Fix

State the compilers that are actually supported and tested — GCC
(Linux), Clang (macOS), and clang-cl with the MSVC toolchain (Windows) —
and drop the unverified VS 2019 floor.

Docs-only change.

The build requirements listed "MSVC >= VS 2019", but CI never builds
with the MSVC cl compiler. The Windows lane uses clang-cl (clang with
the MSVC ABI) under the MSVC toolchain, because the project's glib
dependency is exercised there via clang-cl, not cl. GCC is covered on
Linux and Clang on macOS. State the compilers that are actually
supported and tested, and drop the unverified VS 2019 floor.
@justinjoy justinjoy merged commit 4ef4bff into main Jun 29, 2026
3 checks passed
@justinjoy justinjoy deleted the docs-readme-windows-compiler branch June 29, 2026 10:10
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.

1 participant