luarocks config variables.CC /my/path/to/gcc
I'm running into an issue now with using a remote repository for my rockserver and using luarocks-admin commands, centered in the using wget over https in luarocks/admin/cache.lua.
When I run luarocks-admin add or refresh_cache with my server specified it runs the following wget through os.execute(cmd):
executing cmd = wget --no-cache -v -m -np -nd -kpN -e robots=off --reject *.rock https://my.repository/rocks/ --user=user --password=password
When run, it downloads the index.html just fine, but as it crawls over the index to download manifests it hits issues that print as:
HTTP request sent, awaiting response... 200 No headers, assuming HTTP/0.9
Length: unspecified
Saving to: ‘manifest-5.1’
but then hangs for several minutes and eventually saves an empty file for manifest-5.1, then repeats the process for the rest of the files.
But, when I run the exact same wget command in the same .cache/luarocks/temp folder, it downloads successfully.
@watchd0g Support for cross-compilation in LuaRocks is not great as of now.
For modules that use the builtin type you can get away with setting a few environment variables (CC, LD, CFLAGS...) but for modules which use make / cmake you typically need to look at each one and do custom stuff. Also you will probably want static builds and LuaRocks is not really made for this either.
I use to maintain a code base that built on several embedded platforms and honestly I had given up on using LuaRocks for this (at least for non-pure modules). I just included all the C modules I needed in my own build system.
If I had to do it today I might look at the possibility of using Zig as the C compiler: https://andrewkelley.me/post/zig-cc-powerful-drop-in-replacement-gcc-clang.html
my_module/init.lua
my_module/utilities/init.lua
my_module/utilities/http.lua
lua folder feature
luarocks make --pack-binary-rock?By default the
*.all.rock file is created in the current directory.I am trying to create an automated build which puts the output in a separate directory and does not contaminate my source directory.
I do this for multiple source directories (each is a different Kong plugin).
I want to later add the separate output directory to the
LUA_PATH
Hi, is there a way to specify output directory for the command luarocks make --pack-binary-rock?
no, this is currently not supported
I want to later add the separate output directory to the LUA_PATH
note, though, that LUA_PATH will not pick up modules inside packed binary rocks
*all.rock file to the output dir. I wanted to avoid having to move the file in a separate command, but oh well.Good point about LUA_PATH and binary packs.
I'll run
luarocks --tree <output_tree_dir> install *.all.rock as the last step of my build and add <output_tree_dir> to LUA_PATH
luarocks binary, because that depends less on the surrounding environment — but it will still try to use msvc/mingw to compile things etc. — so, it's not a recommended or supported way of using LR, but it might be fun to try ;)
luarocks install I can pass a specific URL I want to use as as rockspec, but is there a way to accomplish the same effect inside a rockspec file in the dependencies = {} table? I'm trying to test something in my fork of an upstream module in some downstream software builds before I submit PR(s) and it's really difficult to change the build systems to install a different way.
require('luackocks').install('lua-cjson') or something similar)
