Grouped build options

Quite simply are groups of instructions related to some aspect of the build process, they are stored after the main options in a build file and use the popular INI format:

[GROUP_ID] Parameter = Parameter(s) ...

The format and parameters of the instruction lines are specific to the purpose of the group they reside, of which there are four to choose from: Resources - Execution - Version info & Patching .

Resources

Adding / Removing / Preserving interpreter resources.  [A3C_RES]  Description = Type } Index } Lang } File Go here for parameter information. Example [A3C_RES] Tray Icon  = ICO } 100   } 0 } @SD>Images\Tray.ico Win image  = BMP } WBACK } 0 } @SD>Images\Back.bmp About text = RC  } ABOUT } 0 } @SD>Data\About.txt

Execution

Adding / Removing / Preserving interpreter resources.  [A3C_PBE]  Description = Program } Cmdline } WorkingDir } Exit } Run Go here for parameter information. Example [A3C_PBE] Au3Check     = << @AU3X>  } "@IN>"     } @SD> } 0 } P Au3Stripper  = << @STRIP> } "@IN>" /SO } @SD> } 0 } P Run output   = !  @OUT>   }            } @SD> } 0 } A

Version info

Creating the program version info resource.  [A3C_VER]  VersionName = Version parameter Go here for parameter information. Example [A3C_VER] FileDescription = My awesome program FileVersion     = 1.0.0.0 ProductName     = My program ProductVersion  = 2.0.0.0 MyOwnVerName    = Something something ...

Patching

Searching and replacing strings and other data in the builder or interpreter or both.  [A3C_PAT]  Type = Search } Replace } Target Go here for parameter information. Example [A3C_PAT] U = /AutoIt3ExecuteScript } --Plugin      } I U = /AutoIt3ExecuteLine   } --Snort       } I U = /ErrorStdOut          } --ErrOut      } I U = AutoIt v3 GUI         } My App window } I

The order of the option groups in the config file is not important.

Menu related config groups

A build file can also create its own items for any of the user configurable menus by putting the menu group header plus any items outside the tags that enclose the build options.

If you attempt to put menu item config groups within the build tags or in a build file that does not use tags they will be lost when you save from the interface.

This is just for the hands on users as there is no way to configure/maintain them via the interface.

To save parse time these entrances are only looked for in the first and last build file loaded by AC, otherwise loading build files that reference multiple files takes a considerable amount of time as does menu initialization.

Recommended reference: (CTRL + H or Help toolbar button)

    A3C -> Build config -> File handling

    A3C -> Menu editing

#cs A3C A3C_IN   = MyScript.au3 A3C_INA  = MyScript_stripped.au3 A3C_OUT  = MyApp.exe A3C_ICO    = Main.ico [A3C_RES] My bitmap = BMP } WINBACKGROUND } 0 } Background.bmp [A3C_PBE] Au3Stripper = @STRIP> } "@IN>" } @SD> } 0 } P [A3C_VER] FileDescription = My script FileVersion     = 1.0.0.0 ProductVersion  = 1.0.0.0 [A3C_PAT] U = /AutoIt3ExecuteScript } /RunScript } I [] #ce ;A3C ; Notice the separation of the build options and menus #cs [] #ce ; ConsoleWrite("Source code begins"& @LF)