Large EXE size?

[therevillsParticipant]

Just seeing the sizes of the EXE once a MX2 app has compiled on Windows:

Monkey

[crayon-5cb9b8031fe29940613644 inline="true" ]Function Main() Print "HELLO" End

1 2 3

[crayon-5cb9b8031fe29940613644 inline="true" ]Function Main() Print "HELLO" End

[/crayon]

Debug EXE: 415KB
Release EXE: 203KB

Monkey

[crayon-5cb9b8031fe2e089565885 inline="true" ]Namespace supergame #Import "<std>" #Import "<mojo>" #Import "assets/spaceship_32.png" Using std.. Using mojo.. Class MyWindow Extends Window Field image:Image Method New(title:String, width:Int,height:Int) Super.New(title, width, height, WindowFlags.Resizable) ClearColor = Color.Black SwapInterval=1 LoadStuff() End Method LoadStuff() image = Image.Load( "asset::spaceship_32.png" ) image.Handle=New Vec2f( .5,.5 ) End Method OnRender(canvas:Canvas) Override App.RequestRender() canvas.Color = New Color(.5, .5, .5) canvas.DrawText("Hello World!", 320, 240, .5, .5) canvas.Color = New Color(1, 1, 1) canvas.DrawImage(image, 100, 100) End End Function Main() New AppInstance New MyWindow( "Super Game!",App.DesktopSize.x/2,App.DesktopSize.y/2 ) App.Run() End

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39

[crayon-5cb9b8031fe2e089565885 inline="true" ]Namespace supergame   #Import "<std>" #Import "<mojo>"   #Import "assets/spaceship_32.png"   Using std.. Using mojo..   Class MyWindow Extends Window Field image:Image   Method New(title:String, width:Int,height:Int) Super.New(title, width, height, WindowFlags.Resizable) ClearColor = Color.Black SwapInterval=1 LoadStuff() End Method LoadStuff() image = Image.Load( "asset::spaceship_32.png" ) image.Handle=New Vec2f( .5,.5 ) End Method OnRender(canvas:Canvas) Override App.RequestRender() canvas.Color = New Color(.5, .5, .5) canvas.DrawText("Hello World!", 320, 240, .5, .5) canvas.Color = New Color(1, 1, 1) canvas.DrawImage(image, 100, 100) End End   Function Main() New AppInstance New MyWindow( "Super Game!",App.DesktopSize.x/2,App.DesktopSize.y/2 ) App.Run() End

[/crayon]

Debug EXE: 7235KB (plus DLLs)
Release EXE: 3149KB (plus DLLs)

I know its a new tech, but these EXE sizes look a bit on the large size for these small code samples.

Is there a plan for the future to reduce the size of the EXEs?

[Mark SiblyKeymaster]

There is probably some scope for reducing exe sizes – you could rebuild everything in release mode optimized for size instead of speed for example – but I can’t see it making a huge difference and I wont be doing this by default.

Much of the size will be a ‘one off’ hit, eg: the mingw static libs and SDL etc. Adding code shouldn’t blow things up tooo dramatically.

Creating a self extracting exe of ‘spacechimps’ gives me a 2M exe with I’m OK with.

 

 

[EthernautParticipant]

I’m not near a computer with M2, but if I remember well the majority of the file size is coming from Mojo, if you only include Std it should drop quite a lot.

My guess is that, unlike M1, M2 compiles everything from the source files, even if it’s unused. Makes sense, since the modules are “pre-compiled” (forgive me if I don’t use the correct terms). Seems like the upside is that M2 compiles much, much, much faster than M1 when creating desktop apps.

But I agree, in the long term it would be ideal if some sort of “unused code stripping” becomes available, even if it comes with the price of slower compiling. Maybe we could have “release”, “debug” and “light” builds, light being slower to compile since it would recompile each used module with just the parts of the code actually used.

I imagine that would be very helpful for Emscripten builds,  possibly lowering the download time significantly.

 

 

 

[therevillsParticipant]

We’ll have to test a really large project and see if the size goes up too much.

I’m loving the current speed of MX2 compile times

(Oh BTW I’ve noticed that the “CODE” tag now expands double quotes)

[Author]

Posts