Hi Martin, Binary module loading is almost working completely. Luvit/Lit's require module will automatically try and load .so or .dll modules on the fly. Try placing the shared object into a 'lib' folder.
[1]https://github.com/virgo-agent-toolkit/lua-sigar/tree/master [2]https://github.com/virgo-agent-toolkit/rackspace-monitoring-agent/blob/fixes/binary_module_build/Makefile[1] [3]https://github.com/luvit/luvit/blob/luvi-up/deps/require.lua#L179 On Mon, Mar 2, 2015, at 07:16 AM, Martin Croome wrote: > Has any thought been given to how one might distribute a native (C) > module with lit? From my own perspective I would like to distribute > compiled binaries rather than building on the destination platform > since I will not have a compiler/toolchain available on it. What seems > to be needed is a way of indicating the appropriate file for the > target architecture. I guess I will look at adding this to lit unless > someone already has something underway or objects to this plan! > > Thanks > > -- > You received this message because you are subscribed to the Google Groups "luvit" group. > To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. > For more options, visit https://groups.google.com/d/optout. Links: 4. https://github.com/virgo-agent-toolkit/rackspace-monitoring-agent/pull/680/files -- You received this message because you are subscribed to the Google Groups "luvit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
