AutoHotkey Community

Check for uneccesary dependency resulting in error message.

For AutoHotkey basic only, a more robust method of using software
  armoring tools on your output exe has been implemented through
  the execute 'Run' config parameter by using the 'During Build'
  option.

  This is an extension of the old method HkC used to use by patching
  the default upx string within the compiler, which was at best very
  twitchy.

  This time the compiler executes HotkeyCamo and not the packer direct
  So we gain the following benefits:

  A) More than one program can be executed 'During Build'
  B) The commandline length is not restricted to the upx string length
  C) Entrances identical to normal execution which provides a bit more
     control over the program such as:

   * visibility
   * Explicit program path
   * working directory

  Things to note from this method:

  A) During build execution heritage
   HkC.exe
      Compiler.exe
              HkC.exe
                 Desired Program.exe
                 ...

  Look at either of the following to get a greater understanding:

  A) The packer menu elements in the Execute tab.
  B) The packing example templates from the menu invoked by clicking
     on the 'Input' button in the main tab or the large interface icon

Something that has always bothered me concerning resource string
  types and or string id's was the loss of the last character in
  the string thanks to the Ansi resource update api.

The build config option HKC_BRM can be used with either ANS or UNI
  as a parameter. (Default is Ansi)

Entirely untested but such builds that do not use the exearc header
  will probably work just they won't be protected. (don't blame me)

  Other than that all other elements of HotkeyCamo should work with
  them. (Assuming that the Ahk2Exe commandline has not changed)

  Couple of things to note if you are trying to use HkC with them:

  When packing just use 'Post build' as the run parameter.
  Completely ignore 'During build'.

  You will need to specify the names/paths to the compiler and the
  interpreter since they will likely not be named or located the
  same as the Ahk basic files.

Numerous other little things that caused me to facepalm till I bled :/

  Oh and the examples have been modified to go along with recent fixes,
  check em out if in doubt.

HKC_A2E=c:\yourpath\Ahk2exe.exe
HKC_BIN=c:\yourpath\AutoHotkeySC.bin

/*
HKC_OUT=mcecs_eg.exe
HKC_ICO=RES\HkC_4.ico
; Remember to set this value to your actual version.
HKC_VER=10485
HKC_RND=123456789
HKC_ALT=0
HKC_TMP=0
HKC_PAK=0
HKC_DBG=0
HKC_SUB=0
HKC_EAR=1
; Here you will need to change these 2 values.
HKC_A2E=c:\yourpath\Ahk2exe.exe
HKC_BIN=c:\yourpath\AutoHotkeySC.bin
[HKC_RES]
BIO Bitmap=2`1`0`RES\BIO16.bmp
RCDATA GIF=10`1`0`RES\RAMBO.gif
RCDATA TXT=10`1`0`RES\MSC.txt
[HKC_PBE]
; Edit this if Reshack is not in the directory above HkC!
RH ADD ICON_2=@CDP>ResHacker.exe`-addoverwrite @BIN>,@BIN>,RES\BOMB.ico,ICONGROUP,160,0`@SD>`0
[]
*/