Previous Thread
Next Thread
Print Thread
Page 2 of 2 1 2
Re: MAME 0.219 [Re: Vas Crabb] #116963 02/29/20 12:01 PM
Joined: Feb 2004
Posts: 2,133
Vas Crabb Offline OP
Very Senior Member
OP Offline
Very Senior Member
Joined: Feb 2004
Posts: 2,133
Your bug report is invalid – while we do like it if SOURCES= builds work because they’re useful for developers, they’re not guaranteed to work, and quite a few definitely won't work without additional effort (e.g. hng64.cpp). SOURCES= builds are primarily intended as a time-saving measure for developers working on a small set of drivers/devices at a time, and it’s expected that developers can resolve or work around build issues when using advanced options. We have limited resources, and preparing a release already takes a week. Trying to test and resolve issues with a significant number of SOURCES= configurations would cause that to blow out massively. We simply don’t have the resources to support SOURCES= builds.

But that aside, you didn’t give any information. We’re not mind readers, and we aren’t using our m4d l33t MAMEdev h4xx0r sk1llz to pwn ur b0xx0rz and find out what your build options are. We’re going to assume that, in the absence of any other details, you’re building in a standard configuration. There are two supported subtargets called “tiny” and “virtual”. If you imply you’re doing a “tiny” build and don’t tell us that it’s actually a SOURCES= build, we’re going to assume you’re building the supported “tiny” subtarget. The supported “tiny” subtarget does not include the Gun Sense device. You omitted critical details.

Re: MAME 0.219 [Re: Vas Crabb] #116964 02/29/20 12:52 PM
Joined: Mar 2001
Posts: 16,473
R
R. Belmont Offline
Very Senior Member
Offline
Very Senior Member
R
Joined: Mar 2001
Posts: 16,473
Also, QTDEBUG=0 builds on Linux are not officially supported, in addition to SOURCES= builds not being officially supported and anything with non-standard OPTIMIZE or LDOPTS flags being *really* not supported. If you build MAME and want support, you build it exactly as we ship it.

Re: MAME 0.219 [Re: Vas Crabb] #116965 02/29/20 01:07 PM
Joined: Mar 2002
Posts: 1,128
H
hap Offline
Very Senior Member
Offline
Very Senior Member
H
Joined: Mar 2002
Posts: 1,128
"SOURCES= builds not being officially supported"
Fake news :P No way, we won't unsupport SOURCES= builds, it's too handy for development.

Re: MAME 0.219 [Re: Vas Crabb] #116966 02/29/20 01:31 PM
Joined: May 2004
Posts: 895
D
Duke Offline
Senior Member
Offline
Senior Member
D
Joined: May 2004
Posts: 895
"Not supported" I assume means that you keep the pieces when it breaks, not that support for it will be removed.

Re: MAME 0.219 [Re: Vas Crabb] #116967 02/29/20 01:38 PM
Joined: Mar 2002
Posts: 1,128
H
hap Offline
Very Senior Member
Offline
Very Senior Member
H
Joined: Mar 2002
Posts: 1,128
If it's due to a missing entry or typo in the script file(s), it needs to be fixed.
cuavas fixed cpu.lua here, it possibly fixes Eo's compile error? https://github.com/mamedev/mame/commit/f011a9134d0e0c789db24fa25c798fb2ff9e8387

Or if the build finder is having trouble, you can add the device source file to the SOURCES string.

*edit* ok, that change fixes naomi.cpp SOURCES= build according to Tafoid

Last edited by hap; 02/29/20 01:41 PM.
Re: MAME 0.219 [Re: hap] #116968 02/29/20 04:19 PM
Joined: Mar 2001
Posts: 16,473
R
R. Belmont Offline
Very Senior Member
Offline
Very Senior Member
R
Joined: Mar 2001
Posts: 16,473
Originally Posted by hap
"SOURCES= builds not being officially supported"
Fake news :P No way, we won't unsupport SOURCES= builds, it's too handy for development.


We don't guarantee it'll work for all of the millions of possible drivers/combinations of drivers, and we assume you're smart enough to fix it if you find a problem. That's why I said "not officially supported" rather than "not supported". The latter would indeed be "we're removing the ability".

Regardless, we do not accept bug reports involving it, but we will accept pull requests as Vas said.

Re: MAME 0.219 [Re: Vas Crabb] #116969 02/29/20 05:42 PM
Joined: Dec 2015
Posts: 111
A
AJR Online Content
Senior Member
Online Content
Senior Member
A
Joined: Dec 2015
Posts: 111
The gunsense build failure was an oversight on my part. I originally intended to put all the new skeleton CPUs in one source file (and accompanying header), but then realized that it didn't account properly for differences in interfacing and internal memory structure. Similarly, my unfinished first draft of 78K family disassemblers had 78K/III and 78K/IV sharing as much code as possible with 78K/I and 78K/II, but that approach turned out to be too messy to continue with due to architectural differences and many deleted instructions. (A 78K/IV disassembler isn't included now, but I left hooks in the 78K/III disassembler so I could still derive it from that.)

Re: MAME 0.219 [Re: Vas Crabb] #116970 02/29/20 06:09 PM
Joined: Mar 2010
Posts: 138
S
Shoegazer Offline
Senior Member
Offline
Senior Member
S
Joined: Mar 2010
Posts: 138
I too am having issues compiling 0.219 though for different reasons that seem to be Qt related. For all I know this is something on my end, but any ideas or thoughts would be much appreciated. Using linux 5.3 with gcc 9.2.1. Compile log below:

Code
Compiling src/lib/netlist/devices/nld_2102A.cpp...
../../../../generated/osd/modules/debugger/qt/breakpointswindow.moc.cpp:82:1: error: ‘QT_INIT_METAOBJECT’ does not name a type
   82 | QT_INIT_METAOBJECT const QMetaObject BreakpointsWindow::staticMetaObject = { {
      | ^~~~~~~~~~~~~~~~~~
Compiling src/osd/modules/input/input_xinput.cpp...
../../../../generated/osd/modules/debugger/qt/debuggerview.moc.cpp:102:1: error: ‘QT_INIT_METAOBJECT’ does not name a type
  102 | QT_INIT_METAOBJECT const QMetaObject DebuggerView::staticMetaObject = { {
      | ^~~~~~~~~~~~~~~~~~
../../../../generated/osd/modules/debugger/qt/dasmwindow.moc.cpp:110:1: error: ‘QT_INIT_METAOBJECT’ does not name a type
  110 | QT_INIT_METAOBJECT const QMetaObject DasmWindow::staticMetaObject = { {
      | ^~~~~~~~~~~~~~~~~~
Compiling src/lib/netlist/devices/nld_2716.cpp...
qtdbg_sdl.make:464: recipe for target '../../../../linux_gcc/obj/x64/Release/qtdbg_sdl/generated/osd/modules/debugger/qt/breakpointswindow.moc.o' failed
make[2]: *** [../../../../linux_gcc/obj/x64/Release/qtdbg_sdl/generated/osd/modules/debugger/qt/breakpointswindow.moc.o] Error 1
make[2]: *** Waiting for unfinished jobs....
Compiling src/lib/netlist/devices/nld_4006.cpp...
qtdbg_sdl.make:472: recipe for target '../../../../linux_gcc/obj/x64/Release/qtdbg_sdl/generated/osd/modules/debugger/qt/debuggerview.moc.o' failed
make[2]: *** [../../../../linux_gcc/obj/x64/Release/qtdbg_sdl/generated/osd/modules/debugger/qt/debuggerview.moc.o] Error 1
Compiling src/lib/netlist/devices/nld_4020.cpp...
Compiling src/lib/netlist/devices/nld_4066.cpp...
qtdbg_sdl.make:468: recipe for target '../../../../linux_gcc/obj/x64/Release/qtdbg_sdl/generated/osd/modules/debugger/qt/dasmwindow.moc.o' failed
make[2]: *** [../../../../linux_gcc/obj/x64/Release/qtdbg_sdl/generated/osd/modules/debugger/qt/dasmwindow.moc.o] Error 1
Makefile:16: recipe for target 'qtdbg_sdl' failed
make[1]: *** [qtdbg_sdl] Error 2

Re: MAME 0.219 [Re: Vas Crabb] #116971 02/29/20 08:35 PM
Joined: Mar 2001
Posts: 16,473
R
R. Belmont Offline
Very Senior Member
Offline
Very Senior Member
R
Joined: Mar 2001
Posts: 16,473
It looks like your Qt headers are missing or the wrong version. If this is not a cleanly downloaded source tree, do a 'make clean' and try again.

Re: MAME 0.219 [Re: Vas Crabb] #116972 03/01/20 05:53 AM
Joined: Mar 2010
Posts: 138
S
Shoegazer Offline
Senior Member
Offline
Senior Member
S
Joined: Mar 2010
Posts: 138
Thanks RB. This was a clean source tree. However, I recently compiled a custom Qt5 since this distro's version is way outdated. I can't get it to recognize the new version as the default though, so sometimes I run into issues like this and I have to force recognition manually, so it looks like I'll have to do that for mame from now on (I just did and it compiles fine now).

Page 2 of 2 1 2

Who's Online Now
1 registered members (Lord Nightmare), 173 guests, and 3 spiders.
Key: Admin, Global Mod, Mod
ShoutChat Box
Comment Guidelines: Do post respectful and insightful comments. Don't flame, hate, spam.
Forum Statistics
Forums9
Topics8,764
Posts115,179
Members4,889
Most Online890
Jan 17th, 2020
Powered by UBB.threads™ PHP Forum Software 7.7.3