On 31 July 2013 05:01, steve donovan <steve.j.dono...@gmail.com> wrote:
> On Mon, Jul 29, 2013 at 8:20 PM, Hisham <h...@hisham.hm> wrote:
>>
>> It was probably undocumented by oversight! It has been there for a
>> long time, isn't it?
>>
>
> Yes, it certainly applies to any _commands_ , so one can say
>
> install_command = 'lake TREE=$(ROCKS_TREE) install'
>
> work it out from there:
>
> LPREFIX = TREE:match '^.(.-)/lib'
> LLIB = LPREFIX..'/lib/lua/5.1'
>
> and define an install target
>
> target.install {
> file.group{src=lib,odir=LLIB}
> }
>
> At least on Unix, this handles installation for the local and main trees
> fine.
>
> The otherwise excellent introduction to writing portable makefiles for
> LuaRocks (which applies to lakefiles as well)
>
> http://luarocks.org/en/Recommended_practices_for_Makefiles
>
> assumes that the prefix is always '/usr/local'.
It assumes the default is /usr/local, but puts it in variables so they
are overridable from LuaRocks.
> And handling 5.2 is a new
> spin - unfortunately I'm not seeing a LUA_VERSION exported.
>
> A most interesting discussion (if mostly with myself ;)) but it would be
> nice if you could upload the Lake rockspec ;)
Didn't I? I see 1.4.1-1 there in the repo!...
-- Hisham
http://hisham.hm/
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Luarocks-developers mailing list
Luarocks-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/luarocks-developers
