Hmm, seems you had sent the email twice because the first was stuck in google groups moderation. Sorry for causing a double post.
As far as luvit's require system, it should fall-back to the native lua require if luvit can't find something. (that said, the lua system knows nothing about bundled assets in luvi apps). The luvit require system knows nothing about LUA_CPATH and other lua require variables. The two systems are independent. On Tue, Oct 27, 2015 at 8:00 AM, develephant <[email protected]> wrote: > Hi, > > Reading through the Luvi docs I noticed it states support for LuaJIT > extensions. Does this include ffi? and if so how do I handle the following > use case. > > I have a compiled .so (unqlite <http://unqlite.org/>) which has a LuaJIT > binding <https://bitbucket.org/sirpengi/luajit-unqlite> and I'm not sure > where to place it directory wise. No matter where I put it, Luvi just > doesn't pick it up on any paths, though looking at the LUA_CPATH env, it > appears have any entry that should point to the .so (./?.so) relative to > the binary. > > I have successfully used this in a straight LuaJIT project, so I know that > it works. Is this possible with Luvi? > > Thanks in advance. > > Cheers. > > > -- > 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. > -- 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.
