4 ms·
Show HN: Luastatic – Build an executable from a Lua program
- hbbio 11y agoThis is an interesting project, thanks for sharing. Did you explore the possibility to use LuaJIT instead? The ability to do this and also integrate with Terra http://terralang.org/ http://terralang.org/ would create a great project!
- Toenex 11y agoI think this is targeted at the scenario where the developer works in Lua but is deploying to platform without any Lua dependencies. Not sure if it will pull in any used packages though.
- ers35 11y agoLua binary modules are supported by referencing the path to the module's static library and any dependent libraries. Used packages are not automatically pulled in. LuaRocks integration would be interesting: https://github.com/keplerproject/luarocks/pull/264 https://github.com/keplerproject/luarocks/pull/264
- ers35 11y agoLuaJIT will be supported in the future. I will take a look at Terra.
- motiejus 11y agoPretty good size: 214K (on amd64 Linux): $ ls -lhd hello -rwxr-xr-x 1 admin admin 214K Oct 26 09:53 hello $ ldd hello linux-vdso.so.1 (0x00007fff5f5ff000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f10611e7000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f1060fe3000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f1060c39000) /lib64/ld-linux-x86-64.so.2 (0x00007f10614f6000) (edit: formatting)
- unmole 11y agoSimilar project for Python: http://www.pyinstaller.org/ http://www.pyinstaller.org/ Works with multiple source files and supports widely used Python modules out of the box.
- fasteo 11y agoAlso check: Bundle [1], using LuaJIT Luvi [2], which is also able to generate a single file executable and you can include static resources. [1] https://luapower.com/bundle https://luapower.com/bundle [2] https://github.com/luvit/luvi https://github.com/luvit/luvi
- larme 11y agoFor multiple lua files, you can first bundle them into a single lua file using squish.[0] [0]: https://github.com/LuaDist/squish https://github.com/LuaDist/squish
- camperman 11y agoYou can do this in Luajit with the following trick: for f in *.lua; do luajit -b $f `basename $f .lua`.o done ar rcus libmylib.a *.o gcc -o myexe main-stub.c -I/usr/local/include/luajit-2.0 -L/usr/local/lib -lluajit-5.1 -Wl,--whole-archive libmylib.a -Wl,--no-whole-archive -Wl,-E Where main-stub.c looks like this: #include <lua.h> #include <lauxlib.h> #include <stdlib.h> #include <stdio.h> int main(void) { int status, result, i; lua_State *L; L = luaL_newstate(); luaL_openlibs(L); /* load your lua entry point here */ status = luaL_loadfile(L, "mainluafile.lua"); if (status) { fprintf(stderr, "Couldn't load file: %s\n", lua_tostring(L, -1)); exit(1); } result = lua_pcall(L, 0, LUA_MULTRET, 0); if (result) { fprintf(stderr, "Failed to run script: %s\n", lua_tostring(L, -1)); exit(1); } lua_close(L); return 0; } The executables produced are very small because you dynamically link to Luajit and statically link to your own Lua code. I have a full media scheduler running at 100 sites which is only 40k. And it runs like a demon on ARM too.
- 0x01 11y agoThat's a neat trick! Is there any reason you can't do this with luac? I tried the equivalent to what you're doing with luac, but gcc complains that "member libmylib.a(luafunc.o) in archive is not an object". What's the difference between the bytecode generated by luajit compared to luac?
- camperman 11y agoLuajit detects the kind of output file passed to the -b option, in this case .o, and writes the data accordingly. It's actually writing compiled architecture-specific object code here which can be linked into a static library. You can also pass it a .c or a .h extension to get c source or headers. I think luac compiles to bytecode only.
- 0x01 11y agoAh, this explains why running a file on the .o file said it was lua bytecode. This feature of luajit makes it much more appealing. Thanks for the info!
- ifoundthetao 11y agoHa! I remember you from the G-Wan forum days (: I'm so excited to see you're still active!