Errors compiling Mame110 with Mame_Compiler_05

[superbigjay]

Hello,
this is my first mame compile trial and I'm having some problems.

Here's what I did:

- install Mame Compiler 0.5
- Download source for mame 110
- select options
 * Debug
 * clean compile
 * disable Werror (<118u5)

Then click GO (I didn't apply any patch/diff)

3 cfiles give errors while compiling,
and I'n not sur if I can ignore them?

Compiling src/mame.c...
src/mame.c: In function 'fatalerror_exitcode':
src/mame.c:960: warning: 'noreturn' function does return
src/mame.c: In function 'fatalerror':
src/mame.c:946: warning: 'noreturn' function does return
...
Compiling src/cpu/arm7/arm7dasm.c...
src/cpu/arm7/arm7dasm.c: In function 'arm7_disasm':
src/cpu/arm7/arm7dasm.c:591: warning: passing argument 3 of 'DasmCoProc_DT'
discards qualifiers from pointer target type
src/cpu/arm7/arm7dasm.c:591: warning: passing argument 4 of 'DasmCoProc_DT'
discards qualifiers from pointer target type
src/cpu/arm7/arm7dasm.c:603: warning: passing argument 3 of 'DasmCoProc_RT'
discards qualifiers from pointer target type
src/cpu/arm7/arm7dasm.c:603: warning: passing argument 4 of 'DasmCoProc_RT'
discards qualifiers from pointer target type
src/cpu/arm7/arm7dasm.c:611: warning: passing argument 3 of 'DasmCoProc_DO'
discards qualifiers from pointer target type
src/cpu/arm7/arm7dasm.c:611: warning: passing argument 4 of 'DasmCoProc_DO'
discards qualifiers from pointer target type
...
Compiling src/expat/xmlparse.c...
src/expat/xmlparse.c: In function 'doProlog':
src/expat/xmlparse.c:3698: warning: passing argument 1 of
'normalizePublicId' discards qualifiers from pointer target type
...
Finished!
0 Hours 35 Minutes and 51 Seconds Elapsed.

Any help? 
I'm including the whole log windows.


PS:
for my cab, I'm using an AMD4600+.
There some OPTIMIZE options for the compilation.
Should I use NONE, AMD Athlon or Athlon64?

Thanks in advance...
Jay 

[headkaze]

Warnings are okay, don't worry about them. As long as it creates an exe at the end your fine.

BTW You should not have Debug selected if you only wanted to run Mame to play games.

[superbigjay]

Warnings are okay, don't worry about them. As long as it creates an exe at the end your fine.

BTW You should not have Debug selected if you only wanted to run Mame to play games.

I think some exe files weren't generated.
For example, I had a
mamed.exe file, but no mame.exe

But with your comment about the debug switch, I think it's
the mame "D"ebug version right?

I'll try again without the debug option.

Thanks for the nice Apps.  It makes MAME compiling for dummies --> me easy...

PS:
same question as I posted in your mame compiler thread...
for AMD 4600+, should I use optimized for:
- none
- athlon 64
- amd athlon

Jay 

[headkaze]

It's best not to post the same question in two places. As I said in the other thread Mame Compiler can't compile 64 bit version of Mame (yet I'm working on it) as it needs a different compiler.

Debug version when compiled creates "mamed.exe". Debug version is for debugging Mame, so you need to turn off that option.

[superbigjay]

It's best not to post the same question in two places. As I said in the other thread Mame Compiler can't compile 64 bit version of Mame (yet I'm working on it) as it needs a different compiler.

Debug version when compiled creates "mamed.exe". Debug version is for debugging Mame, so you need to turn off that option.

thanks a lot headkaze,

I seem to be able to compile 110, but I don't get the same files, nor the same number of files generated when compiling 118.  In both cases, no errors, only a few warnings

Example between 110 and 118
Filename          110  118
chdman.exe        X      X 
file2str.exe         X      -
jedutil.exe          X      X
ledutil.exe          X      X
makemeta.exe   -       X
mameat.exe       X      X  (optimized for amd athlon)
regrep                -       X
romcmp.exe       X      X
src2html.exe      -       X
srcclean.exe      -       X
-------------------------------------
total files           6      9

my guess is that it is normal and is related to code architecture change between releases.

So I guess my build is fine?

Jay