devkitPro

Not sure how familiar you are with msys2 - on windows there is a start menu entry to launch a msys2 shell under devkitpro. This should be use instead of a windows command prompt for command line tools. Keep in mind that paths are a little different. For instance the c: drive is mounted as /c/ instead of c: and forward slashes “/“ are used for paths.

elhobbs wrote:Not sure how familiar you are with msys2 - on windows there is a start menu entry to launch a msys2 shell under devkitpro. This should be use instead of a windows command prompt for command line tools. Keep in mind that paths are a little different. For instance the c: drive is mounted as /c/ instead of c: and forward slashes “/“ are used for paths.

Not sure how helpful this is. The Updater adds msys2 binaries to the path, make works just fine from cmd shell. The problem here is that someone decided to install some random make rather than use the provided tools. There's no particular need to use the bash shell other than preference.

WinterMute wrote:

elhobbs wrote:Not sure how familiar you are with msys2 - on windows there is a start menu entry to launch a msys2 shell under devkitpro. This should be use instead of a windows command prompt for command line tools. Keep in mind that paths are a little different. For instance the c: drive is mounted as /c/ instead of c: and forward slashes “/“ are used for paths.

Not sure how helpful this is. The Updater adds msys2 binaries to the path, make works just fine from cmd shell. The problem here is that someone decided to install some random make rather than use the provided tools. There's no particular need to use the bash shell other than preference.

Yeah, that wasn't the problem. The problem was there was a typo in one of the script, but thanks anyway.