|
Look on page 140 of "Programming in Lua". There are suggested environment variables for dll and module files. Using the Windows XP interface via "My Computer" properties: Create the environment variables listed below: New Variable name: LUA_PATH Variable value: ?.lua;C:\Program Files\Lua\module\?.lua New Variable name: LUA_CPATH Variable value: C:\Program Files\Lua\lib\?.dll With these settings I put the lua5.1.dll in the Program Files\Lua directory along with Lua.exe. All other dll files go into Program Files\Lua\lib and any .lua modules go into Program Files\Lua\module. > Date: Wed, 30 Jan 2008 12:28:44 +0100 > From: meijer78@gmail.com > To: lua@bazar2.conectiva.com.br > Subject: Re: deployment of app with lua51.dll > > On 30/01/2008, Robert Raschke <rrlua@tombob.com> wrote: > > Unless you have a particular need for DLLs you could always statically > > link Lua into your app. I dislike DLL hell, so that's what I do. I > > go further and statically link in all the Lua modules I need as well. > > I used to do that too, I wanted a self-sufficient Lua executable that > I could use anywhere and anytime. But I found myself recompiling the > whole damn thing whenever I discovered a new library, or when one of > them got updated. Also it's problematic when you want to just try out > some module, if it depends on the Lua dll. I found that to be quite a > hassle after a while, so I'm back to using dll's now. Climb to the top of the charts! Play the word scramble challenge with star power. Play now! |