-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installing LUV via Luarocks under Cygwin x86 #523
Comments
Looks like we should probably be using this instead of having CMake try to guess the name of the intended lib when using Luarocks. Relevant code: Lines 89 to 101 in 464b735
Lines 25 to 33 in 464b735
|
I've tried force
|
Am I a great coder or something now? ^_^ Just changed
|
…d it ourselves LuaRocks can provide LUALIB and LUA_LIBDIR variables which should be better than trying to find the right library file ourselves. Note: it does not provide them if the LuaRocks config setting `link_lua_explicitly` is false, so LuaRocks will give the following warnings in that case: Warning: unmatched variable LUALIB Warning: unmatched variable LUA_LIBDIR These warnings happens on Linux and Mac, since they don't link against the Lua libraries. I'm not sure if there's a clean way to avoid the warnings. Attempts to address luvit#523.
…d it ourselves (#545) LuaRocks can provide LUALIB and LUA_LIBDIR variables which should be better than trying to find the right library file ourselves. Note: it does not provide them if the LuaRocks config setting `link_lua_explicitly` is false, so LuaRocks will give the following warnings in that case: Warning: unmatched variable LUALIB Warning: unmatched variable LUA_LIBDIR These warnings happens on Linux and Mac, since they don't link against the Lua libraries. I'm not sure if there's a clean way to avoid the warnings. Attempts to address #523.
I've successfully installed lpeg,mpack and bit via luarocks, but when calling Install LUV it stops on linking lua.dll.
PKG-CONFIG --LIST-ALL
LUAROCKS CONFIG
INSTALL LOGS
...
The text was updated successfully, but these errors were encountered: