Radek Bartoň

@revelator Thank you for your suggestion. Can you be a little bit more specific what you mean by "w32api" and "mingw-w64 api" ? I've figured out that the [https://github.com/msys2/MSYS2-packages/tree/master/mingw-w64-cross-crt](https://github.com/msys2/MSYS2-packages/tree/master/mingw-w64-cross-crt) recipe...

Thank you @revelator for this information. The Win32 API should be available while WinRT API is not much relevant for WoARM64. Any further details on this topic would be appreciated...

### Issue ``` make[2]: Entering directory '/c/Projekty/MSYS2-packages/mingw-w64-cross-winpthreads/src/build-x86_64-w64-mingw32' /bin/sh ./libtool --tag=CC --mode=compile x86_64-pc-msys-gcc -DHAVE_CONFIG_H -I. -I/c/Projekty/MSYS2-packages/mingw-w64-cross-winpthreads/src/winpthreads/mingw-w64-libraries/winpthreads -I/c/Projekty/MSYS2-packages/mingw-w64-cross-winpthreads/src/winpthreads/mingw-w64-libraries/winpthreads/include -DIN_WINPTHREAD -DWINPTHREAD_DBG=1 -D__USE_MINGW_ANSI_STDIO=0 -Wall -DWIN32_LEAN_AND_MEAN -g -O2 -MT src/libwinpthread_la-barrier.lo -MD -MP -MF src/.deps/libwinpthread_la-barrier.Tpo -c...

### Issue ``` ==> Starting build()... configure: loading site script /etc/config.site checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir...

### Issue ``` make[2]: Entering directory '/c/Projekty/MSYS2-packages/mingw-w64-cross-winpthreads/src/build-aarch64-w64-mingw32' /bin/sh ./libtool --tag=CC --mode=link aarch64-w64-mingw32-gcc -Wall -DWIN32_LEAN_AND_MEAN -g -O2 -no-undefined -version-info 1:0:0 -L./fakelib -Wc,-no-pthread -o libwinpthread.la -rpath /opt/aarch64-w64-mingw32/lib src/libwinpthread_la-barrier.lo src/libwinpthread_la-cond.lo src/libwinpthread_la-misc.lo src/libwinpthread_la-mutex.lo src/libwinpthread_la-rwlock.lo...

Note there is a PR that should update the VS on the AMI pending pytorch/test-infra#1175. I haven't touched it for a while but I can revive it if needed.

Also note, that thre might be a bug in collecting the VS logs that would be helpfull for reporting the issue: The workflow compresses the logs into `C:\Users\runneruser\AppData\Local\Temp\vslogs.zip` file but...

What about the use case when someone is cross-compiling Windows binaries inside WSL host and wants to debug the produced Windows binary using Linux host gdb through WSL interop?

Relates to: - [CUDA incorrectly parsed and invalid options forwarded by cmake · Issue #1865 · pytorch/vision (github.com)](https://github.com/pytorch/vision/issues/1865) - https://discourse.cmake.org/t/cmake-and-cuda-11-7/5896/6 - https://stackoverflow.com/questions/56636714/cuda-compile-problems-on-windows-cmake-error-no-cuda-toolset-found

This feature will require to store the results of the GitHub API requests to some persistent storage identified by time of the request, e.g. into the plugin's cache. I am...