install
what you need on the box, and where the dll goes
from ahk, you need two things
| AutoHotkey v2 | #Requires AutoHotkey v2.0, the 64 bit build |
| the dll and its friends | window.abi.dll, plus blend2d.dll and asmjit.dll beside it |
#Include <path to window>\ahk\Kit.ahkfour lines at the top of Kit.ahk say the lot. set any of them before your first call
| default | what it is | |
|---|---|---|
Kit.Dll | window.abi.dll | one constant, and swapping to the tools dll is this line and nothing else |
Kit.Dir | ..\cpp\bin\x64_Debug | relative to Kit.ahk, where the dll and its dependencies sit |
Kit.AbiVersion | the abi this wrapper was written against | |
Kit.PumpMs | 16 | how often a shown window pumps |
the dll loads lazily, on your first call, and the version is checked right there. a mismatch throws, because the enum values moved at abi 2 and an old dll would fill every one of them with something else
from c++, you build it
no cmake, no generated project files. msvc v143 in vs2022, the desktop development with c++ workload, and the windows 11 sdk
window.test -> window.widgets -> window.core -> blend2dthe dependency direction is one way and it is the whole point of the split. window.core referencing
anything in window.widgets is a build break we want
the vendored source has to be there first, extern/blend2d/ and extern/asmjit/. nothing builds
without them, see what it needs
then
cpp\build.bat [Debug|Release]that is the build entry, and it is the one to use. it points TEMP somewhere writable and it builds the
sln rather than a vcxproj, which are the two traps
the whole wiring walkthrough is building it