Possible batch issue
apense opened this issue · 1 comments
apense commented
Some windows systems actually use gcc.bat to run gcc. This is fine, and everything works the same, but I used to run into an issue of the build(64).bat stopping after the first gcc call when I used this setup. I decided to check it out today, and it seems like if you want to keep running in the original batch file, you need to use "CALL" before calling a batch file. I'm submitting a PR for this, but I'm writing the issue here for reference.
apense commented
Realized this should change niminst instead.