--verbose
might help us figure out what's going on wrong. There might be a bug with dealing with different drive letters, since LuaRocks is mostly tested on Unix (where there are no drive letters) and the Windows CI runs on Appveyor where everything runs off a single drive
--verbose
and paste the full output into gist.github.com then send us a link
luarocks config
may also help
luarocks make
to create a binary rock locally, but I'm curious about the same for source rocks
builtin
and get the list of files from build.modules
) and SCM-agnostic (can't assume git
and use it to get the list of files).
luarocks
tool has gotten better at maintaining multiple lua versions at the same time recently, but when launching lua
to run it, everything always boils down to your environment variables
LUA_PATH_5_3
and LUA_CPATH_5_3
for Lua 5.3 (with unversioned variants LUA_PATH
and LUA_CPATH
as fallbacks), same thing for Lua 5.2, and only the unversioned ones for Lua 5.1
luarocks path --lua-version=5.x
outputs the correct values for the Lua version 5.x you want to use
luarocks path
should lead you in the right direction!
error_message
field for external_dependencies
entries, where the rockspec author could give customized instructions. A slight complicator of putting something like a script
field there would be the fact that system package managers usually need root privileges, while rocks can be installed locally.