0x84 0xCF 0xD9 0xC3 0xD1
Compiling src/osd/modules/debugger/qt/windowqt.cpp...
moc: Invalid argument
Usage: moc [options] <header-file>
-o<file> write output to file rather than stdout
-I<dir> add dir to the include path for header files
-E preprocess only; do not generate meta object code
-D<macro>[=<def>] define macro, with optional definition
-U<macro> undefine macro
-i do not generate an #include statement
-p<path> path prefix for included file
-f[<file>] force #include, optional file name
-nn do not display notes
-nw do not display warnings
@<file> read additional options from file
-v display version of moc
qtdbg_sdl.make:518: recipe for target '../../../../generated/osd/modules/debugger/qt/breakpointswindow.moc.cpp' failed
make[2]: *** [../../../../generated/osd/modules/debugger/qt/breakpointswindow.moc.cpp] Error 1
Makefile:16: recipe for target 'qtdbg_sdl' failed
make[1]: *** [qtdbg_sdl] Error 2
makefile:1285: recipe for target 'linux_x64' failed
make: *** [linux_x64] Error 2
It should work fine under linux. The latest code is is at my own github repository and should be run just fine. What CLI are you using to launch MAME?Does anyone have the MAME Nabu personality working on Linux? I've tried two different bodies of MAME source that claim to support Nabu, but neither works properly. One of them appears to boot, based on server log messages, but shows a screen consisting of the ASCII character range repeated a few times and does not respond to keyboard input. When I reset it (F3) I can briefly see the correct splash screen for Ishkur CP/M before it restarts.
The resulting tree does not contain a src/mame/nabu directory, BTW. I may be missing a step somewhere but I have to explicitly checkout the nabupc_wip branch.
The link is to the github view of the branch that includes my code, to actually clone it localling use:I invoke it with this:
./mame nabupc -window -kbd nabu_hle -hcca null_modem -bitb socket.127.0.0.1:5816
Trying again for a third time with your Github sources, but this did not work yesterday. When I do
The resulting tree does not contain a src/mame/nabu directory, BTW. I may be missing a step somewhere but I have to explicitly checkout the nabupc_wip branch.
git clone https://github.com/brijohn/mame.git
cd mame
git checkout nabupc_wip
Do you get that character display immediately on boot up? You never see a blue screen and the nabu logo? Have you tried just compiling my github repo and running directly from there? I seems there is something wrong with how you are adding the executable to a pre packaged build. I've never done that myself.It occurs to me that I may have the runtime directory setup incorrectly. I was following advice from a third-party to download the prepackaged Windows build and simply replace mame.exe with the linux binary. Can anyone comment on this?
UPDATE: I tried deleting all the configuration files from that Windows build. No change. It's definitely booting, but no usable display or keyboard. I give up. Will put a gun to my head and just use the Windows build on a VMware guest.
Yeah you would need to make a directory called nabupc in the roms folder and then copy the nabupc roms there. Though it does seem like it is starting correctly. what hcca emulator are you using and what is it configured to send to mame? It seems like the nabu emulator might be working but there is an issue with what is being sent over the TCP connection. You could try using '-hcca hcca_remote' instead of the null_mode setup. That should load the standard nabu cycle from nabu.ca if it works then the issue is liekly something wrong with the communication between mame and the hcca emulator you are using.I initially see the blue NABU screen with logo, then it clears to some garbage before redisplaying the blue NABU screen. After a moment with the LEDs blinking it clears to black and white with the NABU logo and 'PLEASE WAIT' in the lower left. Finally, it blinks again and shows the ASCII garbage I posted above. I'll try running from the build area.
UPDATE: The 'roms' subdirectory in your repo is empty, so I cannot simply run from there.
While i don't have plans immediately for support the F18A under mame. If what you want is 80 column mode you can recompile mame using the V9938 VDP instead of the TMS9918. The patches to do so can be found at https://forums.nabu.ca/viewtopic.php?p=742#p742Are there any plans to emulate the F18A graphics adapter? A significant number of NABU owners are running with them.