[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Path change to LUA_CPATH in Lua Binaries
- From: "RJP Computing" <rjpcomputing@...>
- Date: Sat, 23 Aug 2008 11:03:00 -0400
On Sat, Aug 23, 2008 at 3:00 AM, David Manura <email@example.com>
RJP Computing writes:> example LUA_CPATH: ;;?.dll;<lua_dir>\clibs\?.dll;...
> The change I am proposing is to add 'clib' to the LUA_CPATH
In general, this may be a good idea.
However, in the case of Lua for Windows, if it incorporates LuaRocks, the search
paths will be determined by LuaRocks, which redefines the "require" function and
imposes it's own "appdir" isolated per-package directory structure[1-2], similar
to those seen in OS X and elsewhere[3-4]. This differs from the flat directory
structure typical in UNIX, currently used in Lua for Windows, and implied in the
What if you didn't use LuaRocks in the exact way that it was intended and only used it to get new modules. Specifically, I am saying _not_ to use the 'require "luarocks.require"' statement at all. Then use LuaRocks to install the modules into a directory that LfW has already setup, to look in for new modules. I understand that this takes some functionality away, but I think this is about the best way to use LuaRocks in LfW right now.