Previous Thread
Next Thread
Print Thread
Page 33 of 35 1 2 31 32 33 34 35
#104479 - 03/10/16 10:40 PM Re: Can't compile latest MESS? READ THIS THREAD [Re: Just Desserts]  
Joined: Mar 2014
Posts: 19
Squash Offline
Member
Squash  Offline
Member

Joined: Mar 2014
Posts: 19
What is the oldest Visual Studio that can build and debug MAME?

VS2010? VS2013?

Last edited by Squash; 03/10/16 10:43 PM.
#104480 - 03/10/16 11:30 PM Re: Can't compile latest MESS? READ THIS THREAD [Re: Just Desserts]  
Joined: Aug 2015
Posts: 303
Edstrom Offline
Senior Member
Edstrom  Offline
Senior Member

Joined: Aug 2015
Posts: 303
Just got a couple of wierd freezes when running the latest GIT on Ubuntu 14.04, it hogs almost all CPU and sometimes it just freezes the whole window system and I had to reboot once as well. I have tried both a new driver and an old known good single driver build and both has worked like a charm up until now.

Mingw under Win-7 compiles and runs the same drivers nicely, however the load and start up time is about 30 seconds now which is like 3-5 times longer than before.

Both are 64bit and I just add the -debug and -window flags at the command lines. EDIT: Ubuntu is running on an ASUS K52J laptop, Intel Core i5 - 480M @ 2.88Ghz, 4Gb RAM and an AMD Radeon HD 6370M. Mingw runs on a newer DELL laptop with a Core i7 and same or better of the rest.

I'll check the full build now.

Last edited by Edstrom; 03/10/16 11:42 PM.
#104484 - 03/11/16 08:01 AM Re: Can't compile latest MESS? READ THIS THREAD [Re: Just Desserts]  
Joined: Aug 2015
Posts: 303
Edstrom Offline
Senior Member
Edstrom  Offline
Senior Member

Joined: Aug 2015
Posts: 303
Yep, even make SUBTARGET=mess DEBUG=1 REGENIE=1 after a make clean creates a binary, started with './mess64d -debug -window' that will freeze the Ubuntu 14.04 window system when quitting from the debugger in one of my known working driver sessions chosen from the new internal UI. I even had to chicken out via a virtual terminal by Ctl-Alt-Del.

Is it the new UI on Ubuntu that I should avoid and how so? (I just realized that this is probably the wrong thread, sorry...)

#104485 - 03/11/16 09:47 AM Re: Can't compile latest MESS? READ THIS THREAD [Re: Squash]  
Joined: Feb 2004
Posts: 1,734
Vas Crabb Offline
Very Senior Member
Vas Crabb  Offline
Very Senior Member

Joined: Feb 2004
Posts: 1,734
Sydney, Australia
Originally Posted By Squash
What is the oldest Visual Studio that can build and debug MAME?


You really need VS2015 for adequate C++14 support.

#104489 - 03/11/16 12:34 PM Re: Can't compile latest MESS? READ THIS THREAD [Re: Just Desserts]  
Joined: Mar 2001
Posts: 15,492
R. Belmont Offline
R. Belmont  Offline

Very Senior Member

Joined: Mar 2001
Posts: 15,492
USA
And conveniently, VS2015 is the first version where you can get a full-flavor copy for free.

#104503 - 03/11/16 10:37 PM Re: Can't compile latest MESS? READ THIS THREAD [Re: Just Desserts]  
Joined: Aug 2012
Posts: 56
arcadefan Offline
Member
arcadefan  Offline
Member

Joined: Aug 2012
Posts: 56
Having trouble compiling on Ubuntu with the following commandline:

Code:
make -j9 PTR64=1 NOWERROR=1 USE_NETWORK=1 sse4=1 TOOLS=1


I get the following:

Code:
../../../../generated/osd/modules/debugger/qt/windowqt.moc.cpp:13:2: error: #error "This file was generated using the moc from 4.8.6. It"
 #error "This file was generated using the moc from 4.8.6. It"
  ^
../../../../generated/osd/modules/debugger/qt/windowqt.moc.cpp:14:2: error: #error "cannot be used with the include files from this version of Qt."
 #error "cannot be used with the include files from this version of Qt."
  ^
../../../../generated/osd/modules/debugger/qt/windowqt.moc.cpp:15:2: error: #error "(The moc has changed too much.)"
 #error "(The moc has changed too much.)"
  ^
Compiling src/lib/util/unzip.cpp...
../../../../generated/osd/modules/debugger/qt/debuggerview.moc.cpp:13:2: error: #error "This file was generated using the moc from 4.8.6. It"
 #error "This file was generated using the moc from 4.8.6. It"
  ^
../../../../generated/osd/modules/debugger/qt/debuggerview.moc.cpp:14:2: error: #error "cannot be used with the include files from this version of Qt."
 #error "cannot be used with the include files from this version of Qt."
  ^
../../../../generated/osd/modules/debugger/qt/debuggerview.moc.cpp:15:2: error: #error "(The moc has changed too much.)"
 #error "(The moc has changed too much.)"


Any ideas on how to fix this?

#104505 - 03/12/16 12:32 AM Re: Can't compile latest MESS? READ THIS THREAD [Re: Just Desserts]  
Joined: Aug 2012
Posts: 56
arcadefan Offline
Member
arcadefan  Offline
Member

Joined: Aug 2012
Posts: 56
Nevermind. I figured out the problem after. Adding QT_SELECT=5 to the commandline fixed it.

#104536 - 03/13/16 11:26 PM Re: Can't compile latest MESS? READ THIS THREAD [Re: Just Desserts]  
Joined: Mar 2014
Posts: 19
Squash Offline
Member
Squash  Offline
Member

Joined: Mar 2014
Posts: 19
forget about it

Last edited by Squash; 03/14/16 01:37 AM. Reason: fuggedabaudi
#104537 - 03/13/16 11:27 PM Re: Can't compile latest MESS? READ THIS THREAD [Re: Just Desserts]  
Joined: Mar 2014
Posts: 19
Squash Offline
Member
Squash  Offline
Member

Joined: Mar 2014
Posts: 19
forget about it

Last edited by Squash; 03/14/16 01:37 AM.
#104891 - 04/03/16 10:03 AM Re: Can't compile latest MESS? READ THIS THREAD [Re: Just Desserts]  
Joined: Jan 2012
Posts: 607
rfka01 Offline
Senior Member
rfka01  Offline
Senior Member

Joined: Jan 2012
Posts: 607
Bavaria
For me the update in the MSYS64 build tools isn't working ... there was something about it in the shoutbox yesterday that had half scrolled off by the time I saw it.

I'm using the Feb 16 archive, set up as described on http://mamedev.org/tools/

When I try to update via "pacman -Syu", the new packages are downloaded, but I get the following error on many modules befor the update simply dies

Code:
      61 [main] pacman (520) C:\msys64\usr\bin\pacman.exe: *** fatal error - cygheap base mismatch detected - 0x180326400/0x180330400.
This problem is probably due to using incompatible versions of the cygwin DLL.
Search for cygwin1.dll using the Windows Start->Find/Search facility
and delete all but the most recent version.  The most recent version *should*
reside in x:\cygwin\bin, where 'x' is the drive on which you have
installed the cygwin distribution.  Rebooting is also suggested if you
are unable to find another cygwin DLL.
54468701 [main] pacman 6020 fork: child -1 - forked process 520 died unexpectedly, retry 0, exit code 0xC0000142, errno 11
Fehler: Konnte keinen neuen Prozess starten (Resource temporarily unavailable)


There is no other CYGWIN on my machine, and MSYS64 sits in standard c:\msys64

On a different note ... despite being on a fast machine, building all those layout files takes quite a while ... RB mentioned over on MW that
Quote:
All of the layout files (and all of the disk/tape format files) compile regardless of what the actual target is. That's a choice Micko made, because it doesn't generally take long to build those.
... Micko, if it's not too much of a hassle, it would be great if only the relevant layout files, e.g. on single machine builds, would get compiled.

Last edited by rfka01; 04/03/16 10:04 AM.

NCR DMV- DEC Rainbow- Siemens PCD- ITT 3030-Oly People- Acorn A5000- Olivetti M20
Page 33 of 35 1 2 31 32 33 34 35

Who's Online Now
3 registered members (Praxis, Heihachi_73, 1 invisible), 22 guests, and 3 spiders.
Key: Admin, Global Mod, Mod
Shout Box
Forum Statistics
Forums9
Topics8,287
Posts107,112
Members4,728
Most Online225
May 26th, 2014
Powered by UBB.threads™ PHP Forum Software 7.6.0
Page Time: 0.096s Queries: 14 (0.013s) Memory: 5.0331 MB (Peak: 5.2592 MB) Zlib enabled. Server Time: 2017-02-27 13:43:27 UTC