|
- { target: debug, sys: mingw64, env: x86_64 } |
|
- { target: release, sys: mingw64, env: x86_64 } |
|
- { target: release, sys: ucrt64, env: ucrt-x86_64 } |
|
- { target: release, sys: clang64, env: clang-x86_64 } |
|
- { target: release, sys: mingw32, env: i686 } |
... which now is also raising deprecation warnings with msys2-setup for mingw32 and mingw64, see msys2/setup-msys2#644
In the short term, we can keep it (but would possibly see less and less packages being available, as happened with bdb and jsonc for mingw32), or do something similar to the MinGW environment: build a package locally, host it somewhere and download the build env (cached) instead of msys2-setup, ... or drop them (using a different "debug" env for CI binaries, then).
gnucobol/.github/workflows/windows-msys2.yml
Lines 83 to 87 in 5568b8f
... which now is also raising deprecation warnings with msys2-setup for mingw32 and mingw64, see msys2/setup-msys2#644
In the short term, we can keep it (but would possibly see less and less packages being available, as happened with bdb and jsonc for mingw32), or do something similar to the MinGW environment: build a package locally, host it somewhere and download the build env (cached) instead of msys2-setup, ... or drop them (using a different "debug" env for CI binaries, then).