Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Not sure if this is a good idea, but currently when you try to require plugins and they aren't packaged right, they are pretty much silently skipped, and you'll just get a regular "module not found" error without any extra info.
Specifically,
package.loadlib
returns nil plus an error message and we don't do anything with that error message. We could return that error message from the lovr.filesystem searcher, which would look like this on Android:Here we can see that the plugin failed to load because
lua_pushinteger
is missing, maybe the plugin failed to link against the Lua library when it was compiled.It basically takes the
dlerror
error message returned bypackage.loadlib
and includes it like all of the other failure messages. They are kind of noisy though, maybe it should just say "failed to load plugin from luaopen_mylib in mylib.so" and log the full error instead?