MAME Compiler 64 v2.0.197

[headkaze]

I'm having all kinds of errors trying to compile. Trying to compile version 0161 with hiscore. Keep getting the attached error. When I try to compile from command line I get the error "python is not available in path". Any ideas on what is causing this and how to fix it?

The latest Mame Compiler 64 requires the new build tools installed. So you will need to go to downloads tab and download them.

[CapnBry]

For some reason the "-j" parameter is not working. It specifies the number of parallel jobs to run. If anyone has any idea why or how we can solve this please let me know.

EDIT: I just noticed your edit. I believe there is still a problem with this switch not working. I only see two make processes running when I specified 8 parallel jobs. Can anyone confirm?

Yeah I noticed this too, the -j option isn't working at the top level. I see that MameCompiler64 launches make which launches multiple makes, but only one g++ instance at a time. I edited the mame makefile and modified MAKEPARAMS:

Code: [Select]

MAKEPARAMS := -R -j4

It works regardless of the make command line. It does not look like you can set this from the main make command because it doesn't override it, it just sets it. Other options don't appear to be working either because I don't have "Include symbols" checked yet the final executable definitely has symbols in it.

[abispac]

im trying to compile mame .138 but the mame compiler 64 v1.17 wont do the job,and i read that   1.18 will work, but cant find a download for it, can anyone help share it?

[headkaze]

I edited the mame makefile and modified MAKEPARAMS

Thanks for the info. When I get a moment I'll update MC64 to use this method.

im trying to compile mame .138 but the mame compiler 64 v1.17 wont do the job,and i read that   1.18 will work, but cant find a download for it, can anyone help share it?

Check out the "Older Versions of MAME" section at the Mame Compiler 64 homepage

[headkaze]

Okay MC64 has been updated to support multiple jobs again. Compile time for me went from over an hour to 20 minutes 

There is still no official update as there are still a few minor issues left to resolve but for the most part it should be fine to download and start using it to compile Mame 0161+

Note 1. You must download the latest Build Tools to compile again (from the Download tab in MC64). Your MinGW folder structure will now be 'buildtools' with 'src' and 'patch' sub-folders. Also there is a new "Update Build Tools" button which will grab the latest build tools from Git (this will only work after you do the initial "Build Tools" download).

Note 2. If you download Mame and MameUI source at the same time then do a compile you may get an "undefined reference" error when you target a compile for WinUI. If this happens download the MameUI source again then put a tick next to "Clean Compile" and try again.

[abispac]

Check out the "Older Versions of MAME" section at the Mame Compiler 64 homepage

I did, i got the source for mame .138, i downloaded mame compiler64 v1.17, and went i get all together,i get
"make: *** windows32_openpipe(): DuplicateHandle(In) failed (e=6)" right away.
ive tried "You need to download mingw-mame-20121207.exe" as you suggestion on a similar problem , i tried some other mingw version but no succes, i read that v1.18 would do the job but cant seem to find a download for your previews versions.

[Leachdude]

Need help please.  I have read the thread and still can not figure out why I get this message when applying the hi_161.txt patch.

Compiling Mame...
Using Parameters PYTHON_AVAILABLE=python SHELLTYPE=msdos -j6 NOWERROR=1 TARGETOS=windows TARGET=mame OSD=windows PTR64=1
Running 'setup-Qt.bat'
Running 'env.bat'
Running 'init.bat'
Error Compiling Mame.
CompileMame(): The system cannot find the file specified


My directory structure is buildtools with patch and src folders.


What am I missing?   I have tried everything I can think of.

[Yoeddy1]

So will this work with 0.162?  Sounds like there a lot of changes.

Jason

[Jumpstile]

Haven't had any success building .162 yet with MAME Compiler 2.0.161.

 - J*

[headkaze]

Haven't had any success building .162 yet with MAME Compiler 2.0.161.

I didn't have a problem compiling 0162.

[Yoeddy1]

How did you pull down 0.162?  I run it and it's still pulling down 0.161 stuff.

Thanks,
Jason

[headkaze]

How did you pull down 0.162?  I run it and it's still pulling down 0.161 stuff.

As soon as MKChamp updates the hiscore diff I'll update the downloads.

[Jumpstile]

The program does not work if you are trying to compile an arcade only version of MAME. The proper subtarget should be arcade, not MAME for this. Can you add the proper alternate subtargets please?

Compiling src/mess/drivers/vii.c...
Compiling src/mess/drivers/wicat.c...
Compiling src/mess/drivers/xor100.c...
Compiling src/mess/drivers/xavix.c...
Compiling src/mess/drivers/zorba.c...
Archiving libskeleton.a...
Compiling src/mame/mame.c...
Compiling src/version.c...
Building driver list...
Importing drivers from '../../../../../src/mame/arcade.lst'
Compiling generated/mame/mame/drivlist.c...
Importing drivers from '../../../../../src/mame/mess.lst'
13859 drivers found
make[2]: *** No rule to make target `../../../../generated/resource/arcadevers.rc', needed by `../../../../mingw-gcc/obj/x64/Release/mameui.res'.  Stop.
make[1]: Leaving directory `E:/MAMESrc/build/projects/winui/mame/gmake-mingw64-gcc'
Finished!
0 Hours 32 Minutes and 23 Seconds Elapsed.
make[1]: *** [mame] Error 2
make: *** [windows_x64] Error 2

 - J*

[Yoeddy1]

Looks like the 0.162 diff file is up now.  Looks like MC64Setup.exe still contains 0.161. Hopefully the targets are updated soon.

Thanks,
Jason

[Jdurg]

Looking forward to an update.  Got a new laptop for the first time in eight years, so I can't wait to play with the new HLSL options.

[headkaze]

MC64 2.0.162 Released
- Support for "arcade" and "mess" sub targets

[Yoeddy1]

Anybody else hanging up on UnZip 'buildtools.7z' Done?  I can't get an active "OK" button. 

[Jumpstile]

I haven't had to do that. Compiling MAME and MESS as subtargets now works great. Thanks!


 - J*

[Yoeddy1]

So I'm trying this on another PC and am getting the same thing.  What in the world is going on?

I've used this for every release since it came out way back when.

I downloaded and ran MC64setup.exe.

All paths look correct for everything. 

I go to the Download tab and put a checkbox by MAME0162 Source, HiScore diff patch, and Build Tools.

I go to the build options tab and select Auto for optimization, and the subtarget as Arcade.

I go back to the Download tab and click the Download Selected button.

It pulls everything down, but once it gets to the following screen it hangs forever and won't move past Unzip build tools.  (see screenshot).

Is it actually doing something?  My HDD light isn't flickering.  Clicking cancel won't do anything and the OK button is always grayed out.  Is there another process that I'm supposed to run?  I don't even get the point where I can click go to compile or apply the diff patch.

Anything would be appreciated.

Thanks,
Jason

[Yoeddy1]

Looking at the links in the updated version, I see:

http://mamedev.org/downloader.php?file=releases/mame0162s.exe

This ends in a 404.

Shouldn't it be:

http://mamedev.org/downloader.php?file=mame0162/mame0162s.exe

Thanks,
Jason

[Yoeddy1]

Yeah, the MAME source is what's locking it up.  If you select the MAME 0162 source by itself and try to download it, that's what's locking everything up.

Sent you a PM headkaze.

Thanks,
Jason

[headkaze]

Thanks Jason, I've updated it.

[Yoeddy1]

You're welcome.  Thank you! 

Jason

[EMDB]

Why is the file size of the MAME executable increased that much from 0.161 to 0.162? And what exactly are the 'tiny', 'arcade' and default builds compared to the old MAME / MESS ones?

[headkaze]

Why is the file size of the MAME executable increased that much from 0.161 to 0.162? And what exactly are the 'tiny', 'arcade' and default builds compared to the old MAME / MESS ones?

As per the whatsnew_0162.txt

As of 0.162 the MAME and MESS projects have been combined into a single emulator.

-MAME now represents full build, for building MESS drivers only use
 make SUBTARGET=mess, for building only Arcades
 drivers only use: make SUBTARGET=arcade [Miodrag Milanovic]

[EMDB]

Thanks. I expected something like that but the Arcade version is still WAY bigger than the previous version (121 MB against 89 MB) 

[Yoeddy1]

Headkaze, it's working great on my end now.  Just finished compiling 0.162 (arcade sub-target).

One bit of feedback for the next release...

The high score patch points to a .diff file by default.  What gets downloaded is a .txt file.  I always have to manually browse to and select the .txt file, otherwise the patching process fails.  A user may not know to do that.

Thanks,
Jason

[MydknyteStyrm]

Thanks for a great program! I am having a bit of trouble though. I can download and get the system to compile Mame 0162, but it hasnt finished yet. Right now its been over five hours, and all four of my cores are at 100%, making the computer slow to a crawl. I have a i5-4670k and I am trying to compile a 32bit version of Mame 0162 on Windows 7 Ultimate 64bit. The reason I want to go with 32 is because my Aimtraks dont seem to work in 64 bit Mame.

The question I have is, what would be the optimal settings on my Build Options tab for my system? What should the SubTarget be? I had the Optimize=AutoDetect, and left everything unchecked except for No Warnings as Errors. Should the Optimize Level be at 0? Any insight would be greatly appreciated. Thanks!

[Jumpstile]

Thanks for a great program! I am having a bit of trouble though. I can download and get the system to compile Mame 0162, but it hasnt finished yet. Right now its been over five hours, and all four of my cores are at 100%, making the computer slow to a crawl. I have a i5-4670k and I am trying to compile a 32bit version of Mame 0162 on Windows 7 Ultimate 64bit. The reason I want to go with 32 is because my Aimtraks dont seem to work in 64 bit Mame.

The question I have is, what would be the optimal settings on my Build Options tab for my system? What should the SubTarget be? I had the Optimize=AutoDetect, and left everything unchecked except for No Warnings as Errors. Should the Optimize Level be at 0? Any insight would be greatly appreciated. Thanks!

Try disabling your AV and try it.

 - J*

[MydknyteStyrm]

That did the trick. Thanks so much!


Sent from my iPhone using Tapatalk

[Jumpstile]

Cool. Same exact thing happened to me. What AV do you use?


 - J*

[MydknyteStyrm]

I have Norton installed


Sent from my iPhone using Tapatalk

[Jumpstile]

Interesting. I use Webroot. Headkaze, is this an issue you have run across? I can't compile anything with my AV turned on using MAME Compiler. Turning it off isn't a big deal, but just curious. Thanks again!!


 - J*

[jaquer]

Hey all.

I'm getting an error trying to get 0.158 to compile. I'm getting errors about linking PortMidi. Am I supposed to compile that separately?

I installed the buildtools first, using the install.exe from mamedev.org/tools. I've tried using the 0.158 source from git (checked out the mame0158 tag) and from mame0158s.zip. I've tried the compile with and without the hi_158 diff.

I'm running W7 Ultimate 64 bit, trying to build a 32bit target for an XP machine. All MC build options are set to off, except "No Warnings as Errors".

I'm targeting this build because this is the romset I have access to.

Any help is greatly appreciated.

Code: [Select]

Linking mame...
obj/windows/libosd.a(portmidi.o):portmidi.c:(.text+0x89): undefined reference to `Pm_GetDefaultInputDeviceID'
Finished!
1 Hours 23 Minutes and 44 Seconds Elapsed.
obj/windows/libosd.a(portmidi.o):portmidi.c:(.text+0xe9): undefined reference to `Pm_GetDefaultOutputDeviceID'
obj/windows/libosd.a(portmidi.o):portmidi.c:(.text+0x1b4): undefined reference to `Pm_GetDefaultInputDeviceID'
obj/windows/libosd.a(portmidi.o):portmidi.c:(.text+0x2b4): undefined reference to `Pm_GetDefaultOutputDeviceID'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0xfe): undefined reference to `pm_alloc'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0x1ec): undefined reference to `pm_init'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0x2a5): undefined reference to `pm_init'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0x302): undefined reference to `pm_init'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0x4e5): undefined reference to `pm_init'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0x514): undefined reference to `pm_term'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0xf74): undefined reference to `pm_alloc'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0x107b): undefined reference to `pm_free'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0x1096): undefined reference to `pm_free'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0x1114): undefined reference to `pm_alloc'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0x11f1): undefined reference to `Pt_Started'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0x11fc): undefined reference to `Pt_Time'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0x1221): undefined reference to `pm_free'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0x1248): undefined reference to `Pt_Start'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0x1342): undefined reference to `pm_free'
D:/games/MAME/buildtools/vendor/mingw32/bin/../lib/gcc/i686-w64-mingw32/4.9.2/../../../../i686-w64-mingw32/bin/ld.exe: obj/windows/libportmidi.a(portmidi.o): bad reloc address 0x0 in section `.data'
collect2.exe: error: ld returned 1 exit status
make: *** [mame] Error 1

Edit: Got it working. The error had to do with the 32-bit cross-compile. I edited env.bat to force using MinGW32 and I was able to link the executable.

[roknrol]

Trying to download MinGW from MC site results in a 404 at GitHub. Same when trying directly from mamedev.org. Was able to find the mingw-mame-20121207.exe at mameworld.info, though.

Should be good, right? Trying to compile .151 if that makes a difference.

[Robbbert]

Thanks. I expected something like that but the Arcade version is still WAY bigger than the previous version (121 MB against 89 MB) 

You need to strip out the symbols.

Add the option STRIP_SYMBOLS=1 on your make line.

[headkaze]

Mame Compiler 64 v2.0.163 Released
- Added support for STRIP_SYMBOLS

This option is on by default as it will reduce the MAME binary substantially (ie. 118 MB vs 167 MB for a vanilla 64-bit build)

[Yoeddy1]

Worked fantastic with 0.163!  Thanks headkaze!

Jason

[Pitou]

Hello,

Does anyone know the difference between the Arcade and Tiny options in the compiler?

Also, is it possible to compile without the small embedded menu in mame?

Thank you.

Pitou!

[delt31]

....actually I"m making some progress......