libraries:machine_code:mcl

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
libraries:machine_code:mcl [2023-12-17 02:11] – Add more examples geeklibraries:machine_code:mcl [2023-12-17 03:08] (current) – Fix broken markup geek
Line 1: Line 1:
 ====== MCL [v1][v2] ====== ====== MCL [v1][v2] ======
- 
-A new kind of machine code library for AutoHotkey. 
  
 THIS IS ALPHA SOFTWARE THIS IS ALPHA SOFTWARE
  
-Currently only supports AutoHotkey V1 U32/U64.+MCL is a new kind of machine code library for AutoHotkey, which takes a no-nonsense approach to converting compiled code to AutoHotkey embedded machine code. It requires a GCC-based cross-compiler installed under PATH (named as gcc.exe/%%g++%%.exe or x86_64-w64-mingw32-gcc.exe/x86_64-w64-mingw32-%%g++%%.exe) to run the tests, examples, or to compile any code. 
 + 
 +It was designed to work with mingw-w64 installed via [[https://www.cygwin.com/|Cygwin]], and mingw-w64 installed via [[https://www.msys2.org/|MYSYS2]], but has been tested to work with [[https://jmeubank.github.io/tdm-gcc/|TDM-GCC]] as well. 
 + 
 +Once your C or %%C++%% code has been compiled to a standalone function or class, that standalone class will have no dependency back to MCL. Scripts using your compiled code will need to include //just// the compiled code, and nothing else. You can check the releases of [[libraries:json:cjson]] for an example of what compiled code would look like in a script. 
 + 
 +MCL has a few extra features compared to other machine code tools, the big ones being: 
 + 
 +  * Support for both C and %%C++%% 
 +  * Includes some basic hand-written replacements for some of the most common standard headers 
 +  * Support for both 32 and 64 bit 
 +  * Allows very large constants (and Doubles, which GCC tends to promote to being a global constant, breaking code under other tools) 
 +  * Allows exporting one or more functions to AutoHotkey 
 +  * Allows exporting one or more global variables to AutoHotkey 
 +  * Generates a wrapper with all the DllCalls/NumGet/NumPut calls pre-bound with offsets and types 
 +  * Allows importing functions from external DLLs into the C/%%C++%% code, such as from the Windows API or any other DLL you have laying around 
 +  * Generates standalone AutoHotkey code with the compiled machine code and wrappers, so you can include compiled code without including the MCL library. 
 + 
 +Altogether, MCL has just enough features that a solid subset of standard C code can be compiled under it, and run (more or less) fine. 
 + 
 +The primary goal of MCL is to enable much more complex machine code functions/libraries without resorting to a dll. For example [[libraries:json:cjson]] which is compiled under MCL, and makes use of global variables, "exporting" multiple functions, and floating point numbers. 
 + 
 +MCL also supports a tiny subset of %%C++%% (no STL, exceptions, or RTTI). For example, see [[https://github.com/G33kDude/MCL.ahk/blob/main/Tests/CPP/Spooky.cpp|the SpookyHash test]], which uses a %%C++%% implementation of the [[https://burtleburtle.net/bob/hash/spooky.html|SpookyHash]] hashing algorithm. 
 + 
 +MCL also adds the ability for code to "import" functions from DLLs in the same way you can with ''DllCall''. This feature doesn't replace DLL files, and isn't the primary goal of the project. Just think of it as a cherry on top. 
 + 
 +And a (low level) warning for this feature: There is a bug with mingw-w64 compilers which results in the stack being misaligned, which will cause a crash the next time a Windows API (or standard library) function is called from your C/%%C++%%. This bug can be tracked [[https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412|here]]. 
 + 
 +For an example of "importing" functions, see [[user:cloakersmoker]]'s [[https://github.com/CloakerSmoker/PDFGen.ahk|PDFGen example library]], which uses a regular C library with a few headers changed around along with an incredible number of imported standard library functions. 
 + 
 +----
  
-Requires a gcc-based Windows %%C/C++%% compiler (for example, mingw-w64). MSVC is not supported.+If you have any questions about the library, please feel free to join [[https://geekdude.io/discord|the Discord]] and ping [[user:geek]] or [[user:cloakersmoker]] in ''#mcl-mcode-lib''.
  
 If you run into any problems, please report them as GitHub issues. If you run into any problems, please report them as GitHub issues.
Line 56: Line 84:
 In AHK, MCL provides all functionality through the ''MCL'' class.  In AHK, MCL provides all functionality through the ''MCL'' class. 
  
-Any method which is described as "returning compiled code" returns an object that wraps the exported functions and global variables as methods and properties respectively. The object is also callable, in which case it will invoke any export named "main".+Any method which is described as "returning compiled code" returns an object that wraps the exported functions and global variables as methods and properties respectively. The object is also callable, in which case it will invoke any export named "%%__main%%".
  
 Now, for the API: Now, for the API:
Line 67: Line 95:
 For any method which takes an ''Options'' parameter, the following options can be provided to control the bitness/format of the generated code: For any method which takes an ''Options'' parameter, the following options can be provided to control the bitness/format of the generated code:
  
-  * ''MCL.Options.OutputAHKBit'' generates code which will run in `A_PtrSize * 8` AHK. So, on AHK U32, this flag tells MCL to generate 32 bit code. On AHK U64, this flag tells MCL to generate 64 bit code.+  * ''MCL.Options.OutputAHKBit'' generates code which will run in ''A_PtrSize * 8'' AHK. So, on AHK U32, this flag tells MCL to generate 32 bit code. On AHK U64, this flag tells MCL to generate 64 bit code.
   * ''MCL.Options.Output32Bit'' generates 32 bit code, ignoring the bitness of the AHK executable.   * ''MCL.Options.Output32Bit'' generates 32 bit code, ignoring the bitness of the AHK executable.
   * ''MCL.Options.Output64Bit'' generates 64 bit code, ignoring the bitness of the AHK executable.   * ''MCL.Options.Output64Bit'' generates 64 bit code, ignoring the bitness of the AHK executable.
Line 433: Line 461:
 </runner> </runner>
 </tabbox> </tabbox>
 +
 +==== Import DLL with Headers (Lua) ====
 +
 +<runner ahk2>
 +#Requires AutoHotkey v2
 +#DllLoad Z:\ahk2\lua\lua54.dll
 +#Include <MCL>
 +FileCopy "Z:\ahk2\lua\include\*.h", A_WorkingDir
 +
 +lib := MCL.FromC("
 +(
 +#include <mcl.h>
 +#include <stddef.h>
 +#include <string.h>
 +#include "lua.h"
 +#include "lauxlib.h"
 +#include "lualib.h"
 +
 +#define MCL_IMPORT_SOURCE lua54
 +
 +MCL_IMPORT_DECLARED_FROM(luaL_newstate);
 +MCL_IMPORT_DECLARED_FROM(luaL_openlibs);
 +MCL_IMPORT_DECLARED_FROM(luaL_loadstring);
 +MCL_IMPORT_DECLARED_FROM(lua_pcallk);
 +MCL_IMPORT_DECLARED_FROM(lua_close);
 +
 +lua_State *L;
 +
 +MCL_EXPORT(init, Int)
 +void init() {
 +    L = luaL_newstate();
 +    luaL_openlibs(L);
 +}
 +
 +MCL_EXPORT(dostring, AStr, str, Int)
 +int dostring(char* str) {
 +    return luaL_loadstring(L, str) || lua_pcall(L, 0, 0, 0);
 +}
 +
 +MCL_EXPORT(close, Int)
 +void close() {
 +    lua_close(L);
 +}
 +)")
 +
 +lib.init()
 +lib.dostring('print("Hello from Lua!")')
 +lib.close()
 +</runner>