 |
lua-l archive |
|
|
||
|
Thanks for this too. It looks like another rabbit hole for me to dive into. However you mention "executable using salsa", could you provide a link as "lua salsa executable" and variations on this bring up nothing usable (unless I was searching for a dip)On Mon, 26 Jul 2021 at 15:25, Milind Gupta <milind.gupta@gmail.com> wrote:I use this Lua script[1] I made to combine all Lua dependencies into a single Lua script. It automatically scans the Lua program being packaged and its dependencies recursively and includes all the Lua code and also copies over all the dynamic libraries to a specified directory to create a self contained package containing just 1 Lua file.Finally I usually just make it an executable using salsa.On Mon, Jul 26, 2021, 4:19 AM Peter Hickman <peterhickman386@googlemail.com> wrote:Thanks for this, it is very interesting but at the moment I don't want files I have forgotten to include in the build from being picked up. As the only time I will notice that I have forgotten to include something is when I try to deploy itHaving said that when things get bigger (and the edit, build, compile loop takes longer) this technique looks interesting. Perhaps I should include a switch for development vs production?Again thank for sharing this