Closed TheShermanTanker closed 1 month ago
Those are GUI launchers, they wont do what you want in CI.
Not sure what you are trying to do, or what you want, but you just pass "msystem" to the action, and then the "msys2" command will launch bash with the right environment.
I currently have a workflow that needs to use one of the launchers themselves (mingw64.exe and so on, bash by itself won't cut it since the workflow depends on the environment the launcher provides), but setting the path and doing
shell: mingw64 . {0}
(which seems to be how to run the launcher with the file specified) simply doesn't execute anything:(There should be way more log output than the absolute nothingness shown above!)
Is there a way to do this properly? I know the action provides a wrapper msys2.cmd script, but it seems to just directly call bash after setting the usual
CHERE_INVOKING
and so on, which doesn't seem to be what I need