You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've just bumped into a similar iteration of the problem in #2, but at a different spot in the stack. In my case I'm using a Rust wrapper with mlua, and the Rust side of things is injecting a custom loader that actually just outputs content that is statically linked (C modules) or embeded (Lua modules) in the binary itself. This is working for most Lua stuff, but it is now tripping up Loadkit.
In my case the issue is not just that the searcher uses the wrong paths, its that it isn't even hitting the right loader. I can easily provide some sort of function / hook that loadkit can call to get the contents of a file, but I need to feed it the file data not just return an open Lua file pointer to be used by the function supplied to loadkit.register().
The text was updated successfully, but these errors were encountered:
I've just bumped into a similar iteration of the problem in #2, but at a different spot in the stack. In my case I'm using a Rust wrapper with
mlua
, and the Rust side of things is injecting a custom loader that actually just outputs content that is statically linked (C modules) or embeded (Lua modules) in the binary itself. This is working for most Lua stuff, but it is now tripping up Loadkit.In my case the issue is not just that the searcher uses the wrong paths, its that it isn't even hitting the right loader. I can easily provide some sort of function / hook that loadkit can call to get the contents of a file, but I need to feed it the file data not just return an open Lua file pointer to be used by the function supplied to
loadkit.register()
.The text was updated successfully, but these errors were encountered: