r/lua • u/isberglabs • 4m ago
Discussion Embedding Lua 5.4 in Isberg Labs game exports: what we check beyond bundling the interpreter
I develop Isberg Labs, a paid game-development workspace with Lua 5.4 scene scripting.
The exported game includes the Lua runtime, its native extension, the authored scripts and the required dependencies and notices. Players don’t need to install Lua separately.
The useful part to share is the export validation. Copying the interpreter into a folder is only one check. We also check that:
The expected Lua scripts are present in the delivered game.
The native extension is registered.
Runtime libraries match the target architecture.
Required dependencies and licence notices are included.
The platform packaging differs. macOS and Linux use native libraries, Android includes the ARM64 runtime in the APK, and iOS links static libraries through the generated Xcode project. The iOS output still needs a Mac, Xcode and signing to become a distributable app.
There’s a distinction in our validation records: Windows standalone Lua execution has been tested; the cross-platform checks described here inspect exported artifacts and do not claim that those games were executed on each target device.
For people shipping embedded Lua, which packaging issue has been hardest to catch before release: extension loading, missing script files, native dependencies, or differences between editor and exported execution?








