LuaRocks 2.0.4.1
Also allow use with either Lua or LuaJIT This patch lets you install luarocks against either the original Lua interpreter, or against LuaJIT. Lua and LuaJIT are ABI-compatible, so the rocks that you install should be compatible with both interpreters. So we we can use the same path for installed rocks, regardless of which interpreter we build luarocks against. This just affects which interpreter is used to run luarocks itself. Signed-off-by: Adam Vandenberg <flangy@gmail.com>
This commit is contained in:
parent
84d8754d37
commit
f2aa6b2720
1 changed files with 23 additions and 12 deletions
|
@ -1,21 +1,32 @@
|
|||
require 'formula'
|
||||
|
||||
def use_luajit?; ARGV.include? '--with-luajit'; end
|
||||
|
||||
class Luarocks < Formula
|
||||
url 'http://luarocks.org/releases/luarocks-2.0.2.tar.gz'
|
||||
url 'http://luarocks.org/releases/luarocks-2.0.4.1.tar.gz'
|
||||
homepage 'http://luarocks.org'
|
||||
md5 'f8b13b642f8bf16740cac009580cda48'
|
||||
md5 '2c7caccce3cdf236e6f9aca7bec9bdea'
|
||||
|
||||
depends_on 'lua'
|
||||
depends_on use_luajit? ? 'luajit' : 'lua'
|
||||
|
||||
def install
|
||||
fails_with_llvm "Lua itself compiles with llvm, but may fail when other software trys to link."
|
||||
|
||||
def options
|
||||
[['--with-luajit', 'Use LuaJIT instead of the stock Lua.']]
|
||||
end
|
||||
|
||||
def install
|
||||
# Install to the Cellar, but direct modules to HOMEBREW_PREFIX
|
||||
# Configure can detect 'wget' to use as a downloader, but we don't
|
||||
# require it since curl works too and comes with OS X.
|
||||
system "./configure", "--prefix=#{prefix}",
|
||||
args = ["--prefix=#{prefix}",
|
||||
"--rocks-tree=#{HOMEBREW_PREFIX}/lib/luarocks",
|
||||
"--sysconfdir=#{etc}/luarocks"
|
||||
"--sysconfdir=#{etc}/luarocks"]
|
||||
|
||||
if use_luajit?
|
||||
args << "--with-lua-include=#{HOMEBREW_PREFIX}/include/luajit-2.0"
|
||||
args << "--lua-suffix=jit"
|
||||
end
|
||||
|
||||
system "./configure", *args
|
||||
system "make"
|
||||
system "make install"
|
||||
end
|
||||
|
|
Loading…
Reference in a new issue