Different Executable Size

#1 Hi James.

You can do a debug or a release build of the torque engine.
The release build, which has no debug infos is about 1 MB.
The debug build, with all debug infos, symbol tables, etc. in it is about 3 MB.

I don't know how the codesampler executable is build, but different compilers paired with different compiler settings (e.g. optimize for speed/size/..) result in different executable size.

As a matter of fact the size depends on your compiler settings.

-- Markus

#2 If something compiled from the same piece of code varies in size it usually depends on a number of factors: if it's retail or debug, what compiler you use, compiler options (optimization and such), etc...

edit: here i am as usual missing the post before me by a minute or 2 :P

#3 Thanks for the replies.

I have used MS VC6 to compile the engine source code. The executable is a release build, not debug.

I will check out on the compiler settings.

Regards,
James Yong

#4 The demo is also packed with upx before distribution so you won't be able to match its size just with compiler options

#5 @Markus:

Hi,

How can I be able to do a build with no debug info?

In other words: how can I get the executable size as low as possible?

Thanks

#6 Release build with optimize to size ( /O1), favor size over speed and when compiled, do an upx -9 compression.

Should result in the smallest possible executable.

#7 @Marc,

I just don't know how to do that! what is an upx-9 compression?

Can describe the steps to down the 3.3 MB size of my executable?

Thanks!

PS I'm using TBG 1.1.3 tot TGE

#8 I have compressed the 3.3. MB file to 1.37 MB using a protection system that compress the actual exe.

I want to ask if there will be a problem with the game performance doing this. Until I can see, my game is working ok after do this

Thanks

#9 Most exe compression suites only compress it for disk size. When run, it is expanded in memory. You may get some overhead for the expansion process, but that should be it.