> -----Original Message----- > From: steve donovan [mailto:[email protected]] > Sent: vrijdag 5 april 2013 7:55 > To: [email protected] > Subject: Re: [Luarocks-developers] MinGW and LuaSocket > > On Thu, Apr 4, 2013 at 10:45 PM, Thijs Schreijer <[email protected]> > wrote: > > What I did so far was renaming the "liblua.a" generated and > > installed by the Lua makefile to "lua51.lib" and then LuaRocks > > links against that (without errors so far). Am I supposed to > > link against the DLL? > > I think that might 'appear to work', until you do non-trivial things. > liblua.a is the static library, so your extensions get linked statically > against Lua - so you end up with big DLLs that all have Lua cores. I don't > think they will play nice with each other. Standard practice with MinGW > is to link directly against the DLL. (It can link against a .lib or a .a > but that needs to be an import library for the DLL.)
Thinking about that again: when building Lua from source it delivers "lua.exe", "luac.exe", and optionally "lua51.dll". So lua and luac both contain their own Lua core (they don't need the dll iirc). Then even when I link a library against "lua51.dll" I get two Lua-cores loaded at runtime; 1 in lua.exe, 2 in lua51.dll which the library was linked against. So that delivers the same issue of multiple cores? or am I wrong? How to go about resolving this? Thijs ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ Luarocks-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/luarocks-developers
