Complied exe file size

[ShaunWW]

Hi all,

New to AutoIT. Finding it very useful used in conjunction with a PI Engineering Xkey pad. I have one question.

I have an au3 script like this:

#include <AutoItConstants.au3>
#include <FlipLat - Ctrl+L.au3>

; Single middle click at the current mouse position. This gains focus...or not
MouseClick($MOUSE_CLICK_MIDDLE)
; Check if InSight is currently in focus
If WinActive("InSight Local") Then
; followed by the flip horizontal function
   Send("{CTRLDOWN}")
   Send("l")
   Send("{CTRLUP}")
EndIf

 

When complied the exe is nearly 1MB. is there any way this can be reduced?

Thanks, Shaun

[ShaunWW]

...I mean compiled!

Thanks, Shaun

[BrewManNH]

Download Scite4AutoIt3 zip file or Scite4AutoIt3 installer and use the AutoIt3Stripper command to strip out any unwanted data lines from the includes you're using.

#Au3Stripper_Parameters=/so

 

[Au3Builder]

yes.

1) Right click on an au3 script

2) Compile with options

3) Use UPX

Edited February 9, 2018 by Au3Builder

[Melba23]

ShaunWW,

When you "compile" an AutoIt script, you actually add a stripped, tokenised and compressed version of your script to the resource table of an executable containing the entire AutoIt interpreter - hence the size of even a small exe. However, this does allow some interesting options - like running separate .a3x scripts using the interpreter within the compiled exe - and I regard it as a "feature" rather then a "problem".

Using AutoItWrapper and Au3Stripper will remove unwanted functions, but unless your script is seriously large it will not make a huge difference as it merely reduces the size of the resource added. Using UPX will indeed reduce the size of the exe, but experience has shown that it can drastically increase the chance of your compiled script being flagged by your AV - personally I do not use it.

I hope this helps explains why the executable is the size it is - and is 1MB that big these days anyway?

M23

Edit: And welcome to the AutoIt forums.

 

Edited February 9, 2018 by Melba23

[Au3Builder]

42 minutes ago, Melba23 said:

ShaunWW,

When you "compile" an AutoIt script, you actually add a stripped, tokenised and compressed version of your script to the resource table of an executable containing the entire AutoIt interpreter - hence the size of even a small exe. However, this does allow some interesting options - like running separate .a3x scripts using the interpreter within the compiled exe - and I regard it as a "feature" rather then a "problem".

Using AutoItWrapper and Au3Stripper will remove unwanted functions, but unless your script is seriously large it will not make a huge difference as it merely reduces the size of the resource added. Using UPX will indeed reduce the size of the exe, but experience has shown that it can drastically increase the chance of your compiled script being flagged by your AV - personally I do not use it.

I hope this helps explains why the executable is the size it is - and is 1MB that big these days anyway?

M23

Edit: And welcome to the AutoIt forums.

 

it's a thing of the past now.

[Melba23]

Au3Builder,

I would like to believe you, but as I said:

Quote

experience has shown

M23

[Zedna]

I always use UPX together with AutoIt's EXE files and I use exception (white) list in my antivirus software for skipping such directories with my AutoIt's EXE files from scanning and I have absolutely no problems.

[BrewManNH]

3 minutes ago, Zedna said:

I use exception (white) list in my antivirus software for skipping such directories with my AutoIt's EXE

That prevents the issue on your computer, but if UPX'd scripts are being flagged because they used UPX on them, it's still a problem, you're just ignoring it on your computer.