

If you use the Wrapper.ahk version above, you can simply compile Wrapper.ahk with AHK_L and then drop MainScript.ahk, Plugin.ahk, and AutoHotkey.dll in the same directory as the.

This is true for all AHK versions, 1.0, 1.1, 2.0, AHK_H exes bundle the interpreter directly into the exe file, so no end user ever has to have AHK installed and requires no dependencies. But I'm running into some trouble using the compiler shipped with the AHK_H_v2-release, probably the ahk2exe script needs updatingģ. AHK_H can compile scripts, follow HotKeyIt's instructions above. HotKeyIt usually puts out a matching AHK_H release each time Lexikos puts out a new v1/v2 releaseĢ.

It is driven by a custom scripting language that is aimed specifically at providing keyboard shortcuts, otherwise known as hotkeys.
#Autohotkey bundle files for compile software#
AHK_H is a superset built on top of AHK_L, so AHK_H_v2 can interpret all v2 syntax (plus more such as #DllImport). AutoHotkey is a free, open source macro-creation and automation software utility that allows users to automate repetitive tasks. The compiled EXE (And possibly associated files) can be plonked on anyone's disk, and when they click the EXE, regardless of what version of AHK the user has installed (including none), it uses the bundled AHK interpreter.ġ. ahk text files in a specified plugins directoryģ. I can compile an EXE that is able to interpret. User does not, however, need AHK installed or set up in any way.Īny help realizing this goal would be greatly appreciated!Ģ. User can add "panels" that perform arbitrary functions as specified in their ahk script.
#Autohotkey bundle files for compile code#
His code is interpreted, class is extended and he can add a new widget of his derived class to the GUI. User opens my program, clicks "Add Plugin", browses to his. ahk extension text file which extends one of my classes. Sorry if I am unclear, maybe it would help if I described the use-case. Is it an easy process to build my own version? For example, fincs has just released test binaries for the proposed v2 GUI, would it be possible to "bake" that version of AHK into a compiled EXE, such that when AddScript() is executed in the compiled exe, the text file specified by addscript is interpreted by fincs' custom version of AHK, regardless of what version(s) of AHK the end user may have installed? I can use AddScript from within a compiled exe to include the code from an.
