Home Page Forums MAME MAME Can't compile latest MAME? READ THIS THREAD

I'm struggling with compilation of mess using VC 2012(using mingw works fine). I have latest mame sources and buildtools.
My compile.bat looks like this

I'm running compile.bat within buildtools console. I've tried instead of MSBUILD use MSVC_BUILD=1 without luck. I need to get pdb's for debugging inside VC IDE

It seems to me regardless MSBUILD=1 mingw is used and no vmess64d is generated. Thanx

I think I got it. I added parameter vs2012 so my command line looked following



I don't know if all the parameters before vs2012 are neccess
ary (it's not running compilation) I left them there

This cmd creates vs2012 project which could be loaded into VC, there were few compile issues to deal with but fortunately I've managed to get .exe with pdbs. There is also possible to build xp compatible exe(I did not give try)

Merry Christmess to all guys!

I just found the hard way that 7 segment display support ain't included in a build statement like but LED:s and some other artwork features are.

Is there a list of files I need to add to the SOURCES parameter to get a complete artwork support?

Ok so I made it, I set up the Mingw environment and compiled MESS on a 64 bit Windows 7 using the buildtools package and the instructions found on the Tools page. It worked after a few quirks:

I fixed by an additional git config thingie:
I also had to set my HOME environment variable before anything worked
Also the instructions lists two git commands on the same line which will not work.

However, this is soo much easier than my previous two failed attempts to get a Windows environment for MESS/MAME up and running. Thanks a lot for that!:)

For the case where something isn't included automatically on a SOURCES= you just have to manually add that to the SOURCES. For instance, Apple II min-build looks like:

SOURCES=src/mame/drivers/apple2.cpp,src/mame/drivers/apple2e.cpp,src/mame/video/apple2.cpp

It doesn't (or didn't a few weeks ago at least) pick up the video/ file automatically.

yes, I just don't know what other files I need in the SOURCES argument to get the BCD display to work. It do compile and link but the display is dead. Is there a way to get genie to check for unsatisfied requirements or is this hidden by the late bindings?

Also for the record, I got a valuable tip from QMC2 regarding the lack of debugger keyboard short cuts in MAME-169 with Qt5 on Linux. Remove the appmenu-qt5 package and it works again:

If you link successfully, then you are not missing anything.

In order to have an LED display on a driver, you must include a layout file. My recently submitted prophet600.cpp driver shows a pretty simple example with a 2-digit LED display.

Ahh, ok a linktime layout that is? Because it works by just dropping the layout in the artwork folder once the full MESS or MAME binary is used, but I guess it contains already some linked in layouts... That doesn't work right now with the single driver build, which is explained now, thx

You must #include "filename.lh" to establish the link between your driver and the layout (where "filename" is the name of the .lay file), and add MCFG_DEFAULT_LAYOUT(layout_filename) to the machine configuration. Then you're good to go even for single-driver builds.

sorry for my ignorance but ...

i got a

'head' n'est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.
GCC 4.9.1 detected
Building configurations...

...

makefile:830: recipe for target 'windows_x64' failed
make: *** [windows_x64] Error 2

with mingw env

my last good compilation is from 3 january 2016

can someone tell me what i can change to compil again ;-)

thanks in advance