Main > Software Forum
MAME Compiler 64 v2.0.197
Hituro:
I am going to do what Fleskebacon did and try using an older version of MinGW. I have checked the paths for Python, even manually entered the set path for it manually, but it just does not work. I think there just might be a bug with this new MinGW. I'm sure it will be fixed as it just came out earlier this month. I cannot for the life of me see where the code is going awry but then again I'm not exactly a master at coding >.<
Hituro:
So I was able to compile successfully with the previous version of MinGW. I'm pretty sure that there is something wrong with the newest MinGW and the coding for Python is probably the cause.
B2K24:
Newest tools have always worked for me since they got added.
fleskebacon:
Moved the new mingw to another folder, works perfectly.
It's probably getting errors when the path name is getting too long. I can see the python.exe is moved from the bin-folder to opt/bin. Might be just enough for the path name to get too long.
Moved it all down to \mamesrc\mingw-64 and everything's smooth. Thanks!
Jollywest:
I'm having issues compiling MAME 0.155.
I've followed the instructions on the Headsoft website, (apart from the MameUI settings as I'm just want standard MAME), extracted all the necessary files to the correct paths and changed the path names in Mame Compiler to suit.
I've tried MinGW20121207 and MinGW20140905 but I can't get past the error shown in the attachments.
I'm using Windows 8.1 by the way, in case it matters.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version