View Single Post
Old 14th August 2017, 02:18 PM
HatCat's Avatar
HatCat HatCat is offline
Alpha Tester
Project Supporter
Senior Member
Join Date: Feb 2007
Location: In my hat.
Posts: 16,251

Does it work if you leave the `as` lines alone and only do C:\MinGW\bin\gcc.exe?

The batch script still CD'd into the C:\MinGW directory before running `as`, so that shouldn't have to be expanded to C:\MinGW\bin\as.exe. The `cc` probably wasn't working for you because the 32-bit standard MinGW package for Windows has it located elsewhere, and you would just invoke gcc.exe instead if operating from within that directory.

It must have only worked for me because my Windows environment variables had the system path for the installed GNU make utilities for both 64- and 32-bit MinGW. I'm not sure why I left the two files inconsistent with each other; it should be fixed in the latest commit.

I know I did absolutely need to make it C:\MinGW\bin\gcc.exe in the 64-bit make_w64.cmd build script, because just plain cc or gcc being executed relied on the system path finding the 32-bit location instead which was screwing everything up. Effing Windows!
Reply With Quote