VOGONS

size of cvs dosbox.exe

Topic actions

First post, by babylon-shoes

Posted on 
User metadata

finally i compiled dosbox cvs with mingw/msys.

and dosbox.exe is 12MB (!)
and it (seems to) run old dos games ok.

is this normal? 0.63 only had 1.6MB.

i did have to compile SDL from tar ball - configure, make, make install

i did have to use the older directx (from www.libsdl.org/extras/win32/common/directx-devel.tar.gz. newer directx headers for compiling mplayer/mencoder - audio-video - port from linux won't work)

there are other 'packages' in msys "root" which are used with mplayer. would this affect dosbox compilation or its size?

Reply 1 of 5, by ASM

Posted on 
User metadata
Rank Newbie
Rank
Newbie

Did you strip debug information?

Reply 2 of 5, by Qbix

Posted on 
User metadata
Rank DOSBox Author
Rank
DOSBox Author

it's pure the debug information
strip --strip-all dosbox.exe

Water flows down the stream
How to ask questions the smart way!

Reply 3 of 5, by HunterZ

Posted on 
User metadata
Rank l33t++
Rank
l33t++

Side-note: I was once able to use files from a recent DirectX 9 SDK to complie ddraw support in DOSBox, but it was a pain to put the right files in the right places with the right names. I'm not sure if that method produces different code than that generated when using the DirectX files from libsdl.org.

Reply 4 of 5, by babylon-shoes

Posted on 
User metadata

yup, "strip -strip-all dosbox.exe " is the fast-slimming tonic!

btw, methinks the libsdl's directx5 and mplayer uses directx7. never use ms SDK directx9. not brave enough =). also, did not compile with net sdl.

Reply 5 of 5, by HunterZ

Posted on 
User metadata
Rank l33t++
Rank
l33t++

Does mplayer include the DirectX files for MinGW?

I accidentally ran strip on my sdl-config script a couple of times, which caused configure scripts for SDL-using apps to break whenever I ran them.

Go to top of page Go to top of page
Back to DOSBox General
Close window
Close window