[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: Docker based Lua library development
- From: Sean Conner <sean@...>
- Date: Tue, 22 May 2018 21:35:33 -0400
It was thus said that the Great tobias@justdreams.de once stated:
>
> Hi,
>
> when building my own libraries I found it cumbersome to set up some
> framework that allows me to run my stuff and and not install it locally
> which would have contaminated the local installation. Instead I used a
> custom patched version of Lua that extended the package path to something
> relative of the Lua executable (Windows allows that out of the box) and
> run it this way. All this was orchestrated by a rather magical Makefile.
> It seemed cool at the time, elegant even, but in all honesty it was pretty
> convoluted.
So what's wrong with using the environment variables?
[spc]lucy:~>LUA_PATH_5_3="./?.lua" LUA_CPATH_5_3="./?.so" lua-53
Lua 5.3.4 Copyright (C) 1994-2017 Lua.org, PUC-Rio
> print(package.path)
./?.lua
> print(package.cpath)
./?.so
>
-spc