File size after compilation

[RAMzor]

Hi people!

Why compiled files in later version of AutoIt it is more less than in last versions?

For example, I have found in my archive old code from Lazycat EnumIcons.au3 and compiled file size in Autoit 3.1.0.15 - 125.441 bytes.

After code adaptation (some new #include only) for last 3.3.0.0 version file size has 304.815 bytes!?

It is 179.374 (243%!!!) bytes more for same compression type (normal in my case)

Why? Аlso it is normal?

[Melba23]

RAMzor,

Huge changes have occured in AutoIt since 3.1, so I would not be surprised if the code stub were much larger. Look at the difference in size of "C:\Program Files\AutoIt3\Aut2Exe\AutoItSC.bin" between the 2 versions to see (remember that upx will shrink them from their full size).

I see you have added some #include files - they can seriously increase the size of your compiled file. If you use the full SciTE4AutoIt3 install, you can add

#AutoIt3Wrapper_Run_Obfuscator=y

#Obfuscator_Parameters=/SO

to the script and then all unused functions and constants are stripped out (thanks Jos ;-)). That might help reduce the size of your exes as well.

M23

[UEZ]

RAMzor,

Huge changes have occured in AutoIt since 3.1, so I would not be surprised if the code stub were much larger. Look at the difference in size of "C:\Program Files\AutoIt3\Aut2Exe\AutoItSC.bin" between the 2 versions to see (remember that upx will shrink them from their full size).

I see you have added some #include files - they can seriously increase the size of your compiled file. If you use the full SciTE4AutoIt3 install, you can add

#AutoIt3Wrapper_Run_Obfuscator=y

#Obfuscator_Parameters=/SO

to the script and then all unused functions and constants are stripped out (thanks Jos ;-)). That might help reduce the size of your exes as well.

M23

Nice to know the parameters:

#AutoIt3Wrapper_Run_Obfuscator=y

#Obfuscator_Parameters=/SO

Thanks,

UEZ

[RomanK]

Thanks from me, too.

[UEZ]

Anyway, is there any technical reason why the compiled exe is bigger than the previous release?

As far as I remember since the latest Beta version compiled exe gets bigger....

Nice to know

UEZ

[Authenticity]

I guess more error and run-time checking has been added. Anyway it's much smaller than a plain #include <windows.h> C API program compiled using Microsoft Visual Studio for sure ;]

[RAMzor]

...you can add

#AutoIt3Wrapper_Run_Obfuscator=y

#Obfuscator_Parameters=/SO

It has really a little helped and reduced the size from 304.815 bytes to 292.603 bytes (~12Kb less)! Nice to know these parameters

I have applied your trick to other code and have received more considerable difference - more than 110 kb from 398kb to 288kb!

Viva Jos and thanks Melba23!

It should seems to me that this option is must be included by default at compilation. For what to include junk in a code?

Edited January 26, 2009 by RAMzor

[KaFu]

Be aware that /SO means striponly, thus the resulting script is not obfuscated.

Possible Parameters: 
   /cs 0/1   : 0=No String encryption (1=default)
   /cn 0/1   : 0=No Numeric encryption (1=default)
   /cf 0/1   : 0=No Func rename (1=default)
   /cv 0/1   : 0=No Var rename (1=default)
   /sf 0/1   : 1=Strip all unused Func's (0=default)
   /sv 0/1   : 1=Strip all unused Global var records (0=default)
   /striponly: same as /cs=0 /cn=0 /cf=0 /cv=0 /sf=1 /sv=1
   /sci 0   : Default Minimal output to the console: warning and errors.
   /sci 1   : Show more progress information. 
   /sci 9   : Show all debug lines as found in the Obfuscator.log.
   /Beta     : Use Beta Includes. Dont use AutoIt3Wrapper_Run_Obfuscator.
  
To strip the source, which is included in the ouput EXE from all Comments, Whitespace and All un-used Func's (also included UDF's), you just specify :   
/striponly