On Wed, Apr 9, 2025, 07:16 Martin Storsjö <[email protected]> wrote: > This adds an optional github actions workflow, with a number of > smoke test verifications of mingw-w64: > - With an existing release of llvm-mingw, rebuild all the runtimes > - This done for the CRT configurations ucrtbase, ucrt and msvcrt > - Run the llvm-mingw smoke tests on Windows (testing compilation > for all 4 architectures, testing running on x86) > - Run the libcxx testsuite on Windows (i686 and x86_64) > - Test cross-building ffmpeg for all 4 architectures > - Test building and running ffmpeg with its testsuite on Windows > (i686 and x86_64) > - Test building a GCC cross compiler from scratch > - Test cross-building a Windows hosted GCC using the GCC above > - Run a small set of basic tests with the GCC toolchain > > This allows doing some amount of automatic testing of mingw-w64, > covering most common build configurations, avoiding regressing > any of these cases. > > While mingw-w64 isn't primarily hosted on github, this wouldn't > be a mandatory/integrated testsuite per se. But many mingw-w64 > developers do use github and can benefit from this test setup, > and by having it in-repo, it's easier to coordinate updates to > the test configuration when that is needed. It also makes it > easier for others to contribute more testing configurations. >
You're saying that this is optional, and "mingw-w64 isn't primarily hosted on github", but this is one of many small steps to move the project closer there. Github, conversely, is predictably growing further away from maintaining user freedoms since the acquisition by Microsoft. This really isn't a good direction to be going in, and I would ask that you remove this. > _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
