|
Building MAME with Visual Studio 2013.
#325612 - 05/04/14 02:44 PM
|
|
|
OS: Windows 7 64-bit
After installing the following:
1) Visual Studio 2013 Ultimate
2) DirectX SDK
3) MingGW-32 *and* 64 bit versions (to 2 different directories)
4) Latest mame source
I created this batch file which I run from the Visual Studio 2013 | Visual Studio Tools | Developer Command Prompt for Visual Studio 2013 :
set PATH=%PATH%;C:\mingw\mingw64-w32\bin
Set PATH=%DXSDK_DIR%Utilities\Bin\x86;%Path%
Set Lib=%DXSDK_DIR%Lib\x86;%Lib%
Set Include=%DXSDK_DIR%Include;%Include%
MAKE MSVC_BUILD=1 DEBUG=1 SYMBOLS=1 DIRECTINPUT=8 DIRECT3D=9
MAME builds with not a complaint but when MAME starts and you need to select a game, lo and behold the keyboard ENTER key does not work. I can't select a game with the keyboard although double clicking a game with the mouse works.
Is there a solution to this?
I've already looked at the FAQ's.
My next try is to add:
MAMEOS=windows
to the MAKE command line.
|
|
|
| R. Belmont |
|
Cuckoo for IGAvania
|
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 9716
|
|
Loc: ECV-197 The Orville
|
|
|
|
Send PM
|
|
|
Re: Building MAME with Visual Studio 2013.
[Re: tunstals]
#325615 - 05/04/14 03:17 PM
|
|
|
Have you tried launching MAME directly with a game name and seeing if the Enter key then works in the Tab menus? We only support VS2012 right now for VS builds, so it's possible there's a compiler bug, but it's equally possible something broke in the software picker.
|
|
|
|
Re: Building MAME with Visual Studio 2013.
[Re: R. Belmont]
#325652 - 05/05/14 03:17 PM
|
|
|
No, I've not tried that. I will try that tonight. Thanks for your assistance.
I'll report back ASAP.
Scott
Edited by tunstals (05/05/14 03:18 PM)
|
|
|
|
Re: Building MAME with Visual Studio 2013.
[Re: tunstals]
#325859 - 05/12/14 10:21 AM
|
|
|
Unfortunately that approach didn't work either.
|
|
|
|
Re: Building MAME with Visual Studio 2013.
[Re: tunstals]
#325876 - 05/12/14 10:49 PM
|
|
|
> Unfortunately that approach didn't work either.
Does the Enter key work if you start a game from the command line and then press the Tab key to show the menu ?
If not, maybe the setting for UI Select in
Input (general) -> User Interface
is wrong
|
|
|
|
Re: Building MAME with Visual Studio 2013.
[Re: sz72]
#325947 - 05/15/14 01:16 PM
|
|
|
The enter key doesn't work when the game is started from command line, it's strange.
|
|
|
|
Re: Building MAME with Visual Studio 2013.
[Re: tunstals]
#325960 - 05/16/14 08:38 PM
|
|
|
You probably have a configuration problem.
Check that the "UI Select" setting is correct in the user interface control menu.
|
|
|
|
|
Did anyone figure this one out? I'm having the same problem with the same setup.
As an experiment, I tried dragging the exe I built into the folder of a working prebuilt binary, and still had the same problem.
In both cases, pressing enter does nothing, neither does pressing tab to bring up the menu, or using the arrow keys.
It does however respond to pressing letter keys for filtering/searching for games, I just can't start any of them. (image included)
I tried changing the UI select key to something else in the working binary, and then running my exe with that config file but still nothing.
Thanks! Let me know if there's any other information I can provide, or anything else I can try.
Update:
Trying to debug the build from visual studio, giving it a game name as a command line argument. First, I don't see any source files in the solution explorer. When I run the program, it gets to the menu where it asks me to type 'ok', but once again typing doesn't do anything.
(I'm following these instructions http://mamedev.org/devwiki/index.php?title=Building_MAME_using_Microsoft_Visual_Studio_compilers)
Here is the output when I try to debug-run the build:
'vmamed.exe' (Win32): Loaded 'E:\ALEX_STUFF\MahjProj3\MahjProj3\mame\vmamed.exe'. Symbols loaded.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ntdll.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\kernel32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\KernelBase.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\user32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\gdi32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\lpk.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\usp10.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msvcrt.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\advapi32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\sechost.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\rpcrt4.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\sspicli.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\cryptbase.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\winmm.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\shlwapi.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\wsock32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ws2_32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\nsi.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\dsound.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ole32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\powrprof.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\setupapi.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\cfgmgr32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\oleaut32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\devobj.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\comctl32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\dinput8.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\comdlg32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\shell32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\imm32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msctf.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\dbghelp.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\d3d9.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\version.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\d3d8thk.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\dwmapi.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\nvd3dum.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\psapi.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\D3DX9_43.dll'. Cannot find or open the PDB file.
The thread 0xdf0 has exited with code 0 (0x0).
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ole32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Unloaded 'C:\Windows\SysWOW64\ole32.dll'
'vmamed.exe' (Win32): Loaded 'C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\clbcatq.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\MMDevAPI.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\propsys.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\AudioSes.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\avrt.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\hid.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\wintrust.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\crypt32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msasn1.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\wdmaud.drv'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ksuser.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msacm32.drv'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msacm32.dll'. Cannot find or open the PDB file.
'vmamed.exe' (Win32): Loaded 'C:\Windows\SysWOW64\midimap.dll'. Cannot find or open the PDB file.
First-chance exception at 0x7740C42D in vmamed.exe: Microsoft C++ exception: device_missing_dependencies at memory location 0x06B988EC.
First-chance exception at 0x7740C42D in vmamed.exe: Microsoft C++ exception: device_missing_dependencies at memory location 0x06B988BC.
First-chance exception at 0x7740C42D in vmamed.exe: Microsoft C++ exception: device_missing_dependencies at memory location 0x06B98890.
First-chance exception at 0x7740C42D in vmamed.exe: Microsoft C++ exception: device_missing_dependencies at memory location 0x06B98890.
First-chance exception at 0x7740C42D in vmamed.exe: Microsoft C++ exception: device_missing_dependencies at memory location 0x06B988EC.
The thread 0x1a58 has exited with code 2 (0x2).
The thread 0xfb4 has exited with code -1073741510 (0xc000013a).
The thread 0x14b4 has exited with code -1073741510 (0xc000013a).
The thread 0x1684 has exited with code -1073741510 (0xc000013a).
The thread 0xfa4 has exited with code -1073741510 (0xc000013a).
The thread 0x16f0 has exited with code -1073741510 (0xc000013a).
The thread 0x14d8 has exited with code -1073741510 (0xc000013a).
The thread 0x1340 has exited with code -1073741510 (0xc000013a).
The thread 0x1728 has exited with code -1073741510 (0xc000013a).
The thread 0x16e4 has exited with code -1073741510 (0xc000013a).
The thread 0x10ac has exited with code -1073741510 (0xc000013a).
The thread 0x1324 has exited with code -1073741510 (0xc000013a).
The thread 0x160c has exited with code -1073741510 (0xc000013a).
The thread 0x16dc has exited with code -1073741510 (0xc000013a).
The thread 0x870 has exited with code -1073741510 (0xc000013a).
The thread 0x153c has exited with code -1073741510 (0xc000013a).
The thread 0x128c has exited with code -1073741510 (0xc000013a).
The thread 0xa4c has exited with code -1073741510 (0xc000013a).
The program '[3500] vmamed.exe' has exited with code -1073741510 (0xc000013a).
[ATTACHED IMAGE]
Edited by OPAQUeMeGANe (08/25/14 11:25 PM)
|
|
|
Index 
Threaded 
Building MAME with Visual Studio 2013.
Reply
[Re: 
