MSYS2-packages VS qmk_distro_msys

Google says (1, 2, 3) that this issue is caused by Avast/AVG antivirus moving some executable files (bash.exe in your case, seemingly) into its quarantine folder.

It's a known issue: https://github.com/msys2/MSYS2-packages/issues/3150

Could you let me know of this is perhaps relevant to you? I will investigate sometime this week! Thanks for bringing this to my attention.

I am still on WSL1 due to the filesystem performance with WSL2. I recently tried to move more of my workflow towards MSYS2 but various things keep breaking for me without obvious reasons.

Latest issue I encountered was that GNU parallel simple does not work. [1]

[1]: https://github.com/msys2/MSYS2-packages/issues/3289

I've already tested the rest of the tools needed for the build process (just Python 3.10 and PyInstaller) and they seem to work fine. My issue is that both MSYS2 and Cygwin do not work in WINE (this is pretty well documented: MSYS2, Cygwin), so I don't know of any other means of getting the Windows versions of GTK3 libraries in my WINE prefix so that PyInstaller can pack it all up for me.

It's old bug with gcc standard library implementation which has not been fixed, I guess most likely nobody made a bug report. I tested it myself and indeed it doesn't work properly and we are not alone: https://github.com/msys2/MSYS2-packages/issues/1937.

My last experience with MinGW-w64 was when I was trying to compile my C++ simulation code in Windows and finding out that AVX instructions were not working because the compiler had misalignment-related bugs. (The issue is still open in https://github.com/msys2/MSYS2-packages/issues/1209)

MinGW/MSYS certainly had appeal to former Linux devs who didn't want to touch the horrors of MSVC, but Zig (with its included Clang compiler/runtime) might end up being a better solution for people trying to compile C/C++ code on Windows in a stable manner.

- QMK MSYS: you'll need it for many things, for compiling your firmware file and for flashing, especially if flashing with QMK Toolbox isn't permitted in firmware settings (in this case QMK Toolbox just won't recognize your keyboard);

You don't need the GUI though, you can write the simple code yourself, then using QMKMSYS you can compile these flat text files into firmware. Using the appropriate flashing software for ypur microcontroller, you then flash this firmware onto your keyboard.

First, install QMK MSYS from here. Once installation is finished, DO NOT DO "QMK SETUP". I will explain this later.

Download QMKMSYS.exe from https://github.com/qmk/qmk_distro_msys/releases/tag/1.7.2

QMK MSYS: What we will be using to compile the firmware

You don't really need to be able to program though. (Assuming you use Windows) QMK MSYS will help put all the QMK code on your PC and make it ready to make the firmware file, you will just specify which keyboard make & model you have, edit the file line that controls the timing behaviour, and your PC will build the firmware. Then the Toolkit GUI app will help you sync that onto the keyboard.

Download and install latest version of QMK MSYS

a) Installed git for windows. (If you don't know how to use it - don't go this way. Just download qmk-vial as ZIP, extract in "C:\Users\URUsername\qmk_firmware\vial-qmk", install QMK MSYS. Run it from shortcut in installed folder, run "qmk setup -H C:\Users\URUsername\qmk_firmware\vial-qmk" and change directory "cd C:\Users\URUsername\qmk_firmware\vial-qmk" for next steps.) b) Had an error with gh, so installed cli. Cloned qmk-vial with github desktop in the end. c) Had an error with "make", so installed it and cloned submodules. d) Still had an error with "make" when compiling fw "No rule to make target".