Am 23.09.2014 um 21:13 schröbte Hisham: > On 23 September 2014 04:44, Gunnar Zötl <g...@tset.de> wrote: >> Hi, >> >> thanks for the suggestions (and corrections). >> >>> 1) You mention `LUA_LIBDIR` but not `LUALIB`, which is the file name of >>> the Lua library. If you need one, you probably need the other as well >>> (on Linux, *BSD, ..., you need neither). And `LUA_BINDIR` is less useful >>> than `LUA` which is the path to the Lua interpreter. >> >> a note on this: from reading the source (cfg.lua) it would seem that LUALIB >> is >> only defined on windows, and only when using the M$ C compiler. > > I think it was only added there because the builtin build system only > needed it for MSVC... is it a problem?
I think MinGW needs it as well. AFAICS from Lua's Makefile the BSDs, MacOSX, Linux, and AIX (`-bexpall`?) export the Lua symbols from the executable, but Solaris and the generic POSIX target don't. So I'm not sure whether the builtin build mode of LuaRocks actually works on Solaris ... Btw., I have some problems editing the LuaRocks wiki (or registering). Apparently there should be a captcha on the page, but I don't see anything (and Firefox's console doesn't show any errors). > > -- Hisham > Philipp ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Luarocks-developers mailing list Luarocks-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/luarocks-developers
