Further testing. Win / Mac #1

Activity

1. mattsva

   added sub-issues on Oct 9, 2026

   • Windows #2
   • MacOS #3
2. mattsva

   added

   accessibilityBarrier affecting people with disabilitiesBarrier affecting people with disabilities

   good first issueGood for newcomersGood for newcomers

   help wantedExtra attention is neededExtra attention is needed

   on Oct 9, 2026
3. mattsva commented on Oct 11, 2026

   

   mattsva

   on Oct 11, 2026

   ContributorAuthor

   More actions

   Progress update on this umbrella issue.

   All three build systems (Make, CMake, Meson) now build and pass the full 11-test suite on Linux, macOS and Windows in CI (make test workflow: test-make, test-cmake, test-meson, test-platforms × macOS/Windows, test-sanitizers, test-tsan, test-valgrind), plus release.yml produces libmnet artifacts for linux-x86_64, linux-aarch64, macOS and Windows. That work is done and merged (PRs #13–#17).

   Subissue status:

   • Windows #2 (Windows) — CI coverage complete and green; comment posted with what CI proves and the manual steps still needed on a real Windows 10/11 machine. Left open.
   • MacOS #3 (MacOS) — same: CI coverage complete and green; comment posted with the manual steps still needed on a real Mac. Left open.

   What remains for this issue is exactly what it always was: a human running the examples and the library end-to-end on real Windows and macOS installs — linking the shipped DLL/dylib from an external consumer project, running the examples by hand, and reporting anything odd. The self-tests now pass on both platforms automatically, so manual runs should be quick; each subissue has the exact commands.