> > > make -j5 > > > > > > Normal size. > > > > > > VS. > > > > > > make -j5 "SYMBOLS = 1" "SYMLEVEL = 1" > > > > > > Bigger size. > > > > Yes. Bigger size. Symbols contains words. Words for all of the things. > > Using HashMyFiles. > > Using these tools. > > http://www.mamedev.org/tools/ mingw-mame-20121207.exe (32-bit and 64-bit) > > > mame64.exe 952a384cc9e7cb5b738dcc734af737fd 7e49ba1baf71de7e22d32b9717998586d0a29993 > f0981baa L:\UME\mame64.exe 2/7/2014 218 AM 2/7/2014 244 AM 257,153,924 0, 152, 0, 0 > 0.152 exe A > > > 245 MB > > > mess64.exe 7016e9790e090b5a6f59722a1643fd00 ab109596f891310d09728a2bd4ddcbdd12ff736d > d39d3827 L:\UME\mess64.exe 2/7/2014 237 AM 2/7/2014 215 AM 158,575,712 0, 152, 0, 0 > 0.152 exe A > > > 151 MB > > This is from Revision 27519. Compare this size with the Official size.
-----
First off, SYMBOLS=1 is only needed for backtracing a crash, providing line number references from source where execution stopped usually giving a good idea what the problem is.
The official EXE is built to have a minimal compliment of .SYM (symbols), just enough to provide basic information in the form of a stack crawl.
To mirror the official builds, use the following: make OPTIMIZE=3 SYMBOLS=1 SYMLEVEL=1
Of course, you can add your -j3, -j5 or whatever works best. Use TARGET=mess or TARGET=ume for those builds.
When compiled, you can use this to bring the filesize down even more: strip -s mame.exe - again, you can do the same with other binaries produced by providing the filename. This will depending on the .SYM file you created for all lookups
|