1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
4 <title>Installation
</title>
5 <meta http-equiv=
"Content-Type" content=
"text/html; charset=iso-8859-1">
6 <meta name=
"Author" content=
"Mike Pall">
7 <meta name=
"Copyright" content=
"Copyright (C) 2005-2015, Mike Pall">
8 <meta name=
"Language" content=
"en">
9 <link rel=
"stylesheet" type=
"text/css" href=
"bluequad.css" media=
"screen">
10 <link rel=
"stylesheet" type=
"text/css" href=
"bluequad-print.css" media=
"print">
11 <style type=
"text/css">
17 border: 1px solid
#bfcfff;
20 table
.compat tr
.compathead td
{
22 border-bottom: 2px solid
#bfcfff;
24 tr
.compathead td
.compatos
{
27 table
.compat td
.compatcpu
{
29 border-right: 2px solid
#bfcfff;
33 vertical-align: middle
;
36 background-color: #d0d0d0;
42 <a href=
"http://luajit.org"><span>Lua
<span id=
"logo">JIT
</span></span></a>
49 <a href=
"luajit.html">LuaJIT
</a>
51 <a href=
"http://luajit.org/download.html">Download
<span class=
"ext">»</span></a>
53 <a class=
"current" href=
"install.html">Installation
</a>
55 <a href=
"running.html">Running
</a>
58 <a href=
"extensions.html">Extensions
</a>
60 <a href=
"ext_ffi.html">FFI Library
</a>
62 <a href=
"ext_ffi_tutorial.html">FFI Tutorial
</a>
64 <a href=
"ext_ffi_api.html">ffi.* API
</a>
66 <a href=
"ext_ffi_semantics.html">FFI Semantics
</a>
69 <a href=
"ext_jit.html">jit.* Library
</a>
71 <a href=
"ext_c_api.html">Lua/C API
</a>
73 <a href=
"ext_profiler.html">Profiler
</a>
76 <a href=
"status.html">Status
</a>
78 <a href=
"changes.html">Changes
</a>
81 <a href=
"faq.html">FAQ
</a>
83 <a href=
"http://luajit.org/performance.html">Performance
<span class=
"ext">»</span></a>
85 <a href=
"http://wiki.luajit.org/">Wiki
<span class=
"ext">»</span></a>
87 <a href=
"http://luajit.org/list.html">Mailing List
<span class=
"ext">»</span></a>
92 LuaJIT is only distributed as a source package. This page explains
93 how to build and install LuaJIT with different operating systems
97 For the impatient (on POSIX systems):
100 make
&& sudo make install
103 LuaJIT currently builds out-of-the box on most systems.
104 Here's the compatibility matrix for the supported combinations of
105 operating systems, CPUs and compilers:
107 <table class=
"compat">
108 <tr class=
"compathead">
109 <td class=
"compatcpu">CPU / OS
</td>
110 <td class=
"compatos"><a href=
"#posix">Linux
</a> or
<br><a href=
"#android">Android
</a></td>
111 <td class=
"compatos"><a href=
"#posix">*BSD, Other
</a></td>
112 <td class=
"compatos"><a href=
"#posix">OSX
10.4+
</a> or
<br><a href=
"#ios">iOS
3.0+
</a></td>
113 <td class=
"compatos"><a href=
"#windows">Windows
<br>XP/Vista/
7</a></td>
115 <tr class=
"odd separate">
116 <td class=
"compatcpu">x86 (
32 bit)
</td>
117 <td class=
"compatos">GCC
4.x
<br>GCC
3.4</td>
118 <td class=
"compatos">GCC
4.x
<br>GCC
3.4</td>
119 <td class=
"compatos">GCC
4.x
<br>GCC
3.4</td>
120 <td class=
"compatos">MSVC, MSVC/EE
<br>WinSDK
<br>MinGW, Cygwin
</td>
123 <td class=
"compatcpu">x64 (
64 bit)
</td>
124 <td class=
"compatos">GCC
4.x
</td>
125 <td class=
"compatos">ORBIS (
<a href=
"#ps4">PS4
</a>)
</td>
126 <td class=
"compatos">GCC
4.x
</td>
127 <td class=
"compatos">MSVC + SDK v7.0
<br>WinSDK v7.0
<br>Durango (
<a href=
"#xboxone">Xbox One
</a>)
</td>
130 <td class=
"compatcpu"><a href=
"#cross2">ARMv5+
<br>ARM9E+
</a></td>
131 <td class=
"compatos">GCC
4.2+
</td>
132 <td class=
"compatos">GCC
4.2+
<br>PSP2 (
<a href=
"#psvita">PS VITA
</a>)
</td>
133 <td class=
"compatos">GCC
4.2+
</td>
134 <td class=
"compatos compatno"> </td>
137 <td class=
"compatcpu"><a href=
"#cross2">ARM64
</a></td>
138 <td class=
"compatos">GCC
4.8+
</td>
139 <td class=
"compatos compatno"> </td>
140 <td class=
"compatos">Clang
3.5+
</td>
141 <td class=
"compatos compatno"> </td>
144 <td class=
"compatcpu"><a href=
"#cross2">PPC
</a></td>
145 <td class=
"compatos">GCC
4.3+
</td>
146 <td class=
"compatos">GCC
4.3+
<br>GCC
4.1 (
<a href=
"#ps3">PS3
</a>)
</td>
147 <td class=
"compatos compatno"> </td>
148 <td class=
"compatos">XEDK (
<a href=
"#xbox360">Xbox
360</a>)
</td>
151 <td class=
"compatcpu"><a href=
"#cross2">MIPS
</a></td>
152 <td class=
"compatos">GCC
4.3+
</td>
153 <td class=
"compatos">GCC
4.3+
</td>
154 <td class=
"compatos compatno"> </td>
155 <td class=
"compatos compatno"> </td>
159 <h2>Configuring LuaJIT
</h2>
161 The standard configuration should work fine for most installations.
162 Usually there is no need to tweak the settings. The following files
163 hold all user-configurable settings:
166 <li><tt>src/luaconf.h
</tt> sets some configuration variables.
</li>
167 <li><tt>Makefile
</tt> has settings for
<b>installing
</b> LuaJIT (POSIX
169 <li><tt>src/Makefile
</tt> has settings for
<b>compiling
</b> LuaJIT
170 under POSIX, MinGW or Cygwin.
</li>
171 <li><tt>src/msvcbuild.bat
</tt> has settings for compiling LuaJIT with
175 Please read the instructions given in these files, before changing
179 <h2 id=
"posix">POSIX Systems (Linux, OSX, *BSD etc.)
</h2>
180 <h3>Prerequisites
</h3>
182 Depending on your distribution, you may need to install a package for
183 GCC, the development headers and/or a complete SDK. E.g. on a current
184 Debian/Ubuntu, install
<tt>libc6-dev
</tt> with the package manager.
187 Download the current source package of LuaJIT (pick the .tar.gz),
188 if you haven't already done so. Move it to a directory of your choice,
189 open a terminal window and change to this directory. Now unpack the archive
190 and change to the newly created directory:
193 tar zxf LuaJIT-
2.0.4.tar.gz
194 cd LuaJIT-
2.0.4</pre>
195 <h3>Building LuaJIT
</h3>
197 The supplied Makefiles try to auto-detect the settings needed for your
198 operating system and your compiler. They need to be run with GNU Make,
199 which is probably the default on your system, anyway. Simply run:
205 This always builds a native x86, x64 or PPC binary, depending on the host OS
206 you're running this command on. Check the section on
207 <a href=
"#cross">cross-compilation
</a> for more options.
210 By default, modules are only searched under the prefix
<tt>/usr/local
</tt>.
211 You can add an extra prefix to the search paths by appending the
212 <tt>PREFIX
</tt> option, e.g.:
215 make PREFIX=/home/myself/lj2
218 Note for OSX: if the
<tt>MACOSX_DEPLOYMENT_TARGET
</tt> environment
219 variable is not set, then it's forced to
<tt>10.4</tt>.
221 <h3>Installing LuaJIT
</h3>
223 The top-level Makefile installs LuaJIT by default under
224 <tt>/usr/local
</tt>, i.e. the executable ends up in
225 <tt>/usr/local/bin
</tt> and so on. You need root privileges
226 to write to this path. So, assuming sudo is installed on your system,
227 run the following command and enter your sudo password:
233 Otherwise specify the directory prefix as an absolute path, e.g.:
236 make install PREFIX=/home/myself/lj2
239 Obviously the prefixes given during build and installation need to be the same.
242 <h2 id=
"windows">Windows Systems
</h2>
243 <h3>Prerequisites
</h3>
245 Either install one of the open source SDKs
246 (
<a href=
"http://mingw.org/"><span class=
"ext">»</span> MinGW
</a> or
247 <a href=
"http://www.cygwin.com/"><span class=
"ext">»</span> Cygwin
</a>), which come with a modified
248 GCC plus the required development headers.
251 Or install Microsoft's Visual C++ (MSVC). The freely downloadable
252 <a href=
"http://www.microsoft.com/Express/VC/"><span class=
"ext">»</span> Express Edition
</a>
253 works just fine, but only contains an x86 compiler.
256 The freely downloadable
257 <a href=
"http://msdn.microsoft.com/en-us/windowsserver/bb980924.aspx"><span class=
"ext">»</span> Windows SDK
</a>
258 only comes with command line tools, but this is all you need to build LuaJIT.
259 It contains x86 and x64 compilers.
262 Next, download the source package and unpack it using an archive manager
263 (e.g. the Windows Explorer) to a directory of your choice.
265 <h3>Building with MSVC
</h3>
267 Open a
"Visual Studio .NET Command Prompt",
<tt>cd
</tt> to the
268 directory where you've unpacked the sources and run these commands:
275 Then follow the installation instructions below.
277 <h3>Building with the Windows SDK
</h3>
279 Open a
"Windows SDK Command Shell" and select the x86 compiler:
285 Or select the x64 compiler:
291 Then
<tt>cd
</tt> to the directory where you've unpacked the sources
292 and run these commands:
299 Then follow the installation instructions below.
301 <h3>Building with MinGW or Cygwin
</h3>
303 Open a command prompt window and make sure the MinGW or Cygwin programs
304 are in your path. Then
<tt>cd
</tt> to the directory where
305 you've unpacked the sources and run this command for MinGW:
311 Or this command for Cygwin:
317 Then follow the installation instructions below.
319 <h3>Installing LuaJIT
</h3>
321 Copy
<tt>luajit.exe
</tt> and
<tt>lua51.dll
</tt> (built in the
<tt>src
</tt>
322 directory) to a newly created directory (any location is ok).
323 Add
<tt>lua
</tt> and
<tt>lua\jit
</tt> directories below it and copy
324 all Lua files from the
<tt>src\jit
</tt> directory of the distribution
325 to the latter directory.
328 There are no hardcoded
329 absolute path names
— all modules are loaded relative to the
330 directory where
<tt>luajit.exe
</tt> is installed
331 (see
<tt>src/luaconf.h
</tt>).
334 <h2 id=
"cross">Cross-compiling LuaJIT
</h2>
336 The GNU Makefile-based build system allows cross-compiling on any host
337 for any supported target, as long as both architectures have the same
338 pointer size. If you want to cross-compile to any
32 bit target on an
339 x64 OS, you need to install the multilib development package (e.g.
340 <tt>libc6-dev-i386
</tt> on Debian/Ubuntu) and build a
32 bit host part
341 (
<tt>HOST_CC=
"gcc -m32"</tt>).
344 You need to specify
<tt>TARGET_SYS
</tt> whenever the host OS and the
345 target OS differ, or you'll get assembler or linker errors. E.g. if
346 you're compiling on a Windows or OSX host for embedded Linux or Android,
347 you need to add
<tt>TARGET_SYS=Linux
</tt> to the examples below. For a
348 minimal target OS, you may need to disable the built-in allocator in
349 <tt>src/Makefile
</tt> and use
<tt>TARGET_SYS=Other
</tt>. The examples
350 below only show some popular targets
— please check the comments
351 in
<tt>src/Makefile
</tt> for more details.
354 # Cross-compile to a
32 bit binary on a multilib x64 OS
357 # Cross-compile on Debian/Ubuntu for Windows (mingw32 package)
358 make
HOST_CC=
"gcc -m32" CROSS=i586-mingw32msvc- TARGET_SYS=Windows
361 The
<tt>CROSS
</tt> prefix allows specifying a standard GNU cross-compile
362 toolchain (Binutils, GCC and a matching libc). The prefix may vary
363 depending on the
<tt>--target
</tt> the toolchain was built for (note the
364 <tt>CROSS
</tt> prefix has a trailing
<tt>"-"</tt>). The examples below
365 use the canonical toolchain triplets for Linux.
368 Since there's often no easy way to detect CPU features at runtime, it's
369 important to compile with the proper CPU or architecture settings. You
370 can specify these when building the toolchain yourself. Or add
371 <tt>-mcpu=...
</tt> or
<tt>-march=...
</tt> to
<tt>TARGET_CFLAGS
</tt>. For
372 ARM it's important to have the correct
<tt>-mfloat-abi=...
</tt> setting,
373 too. Otherwise LuaJIT may not run at the full performance of your target
378 make
HOST_CC=
"gcc -m32" CROSS=arm-linux-gnueabi- \
379 TARGET_CFLAGS=
"-mfloat-abi=soft"
381 # ARM soft-float ABI with VFP (example for Cortex-A8)
382 make
HOST_CC=
"gcc -m32" CROSS=arm-linux-gnueabi- \
383 TARGET_CFLAGS=
"-mcpu=cortex-a8 -mfloat-abi=softfp"
385 # ARM hard-float ABI with VFP (armhf, requires recent toolchain)
386 make
HOST_CC=
"gcc -m32" CROSS=arm-linux-gnueabihf-
388 # ARM64 (requires x64 host)
389 make CROSS=aarch64-linux-
392 make
HOST_CC=
"gcc -m32" CROSS=powerpc-linux-gnu-
395 make
HOST_CC=
"gcc -m32" CROSS=mips-linux-
397 make
HOST_CC=
"gcc -m32" CROSS=mipsel-linux-
400 You can cross-compile for
<b id=
"android">Android
</b> using the
<a href=
"http://developer.android.com/sdk/ndk/index.html"><span class=
"ext">»</span> Android NDK
</a>.
401 The environment variables need to match the install locations and the
402 desired target platform. E.g. Android
4.0 corresponds to ABI level
14.
403 For details check the folder
<tt>docs
</tt> in the NDK directory.
406 Only a few common variations for the different CPUs, ABIs and platforms
407 are listed. Please use your own judgement for which combination you want
408 to build/deploy or which lowest common denominator you want to pick:
411 # Android/ARM, armeabi (ARMv5TE soft-float), Android
2.2+ (Froyo)
414 NDKVER=$NDK/toolchains/arm-linux-androideabi-
4.6
415 NDKP=$NDKVER/prebuilt/linux-x86/bin/arm-linux-androideabi-
416 NDKF=
"--sysroot $NDK/platforms/android-$NDKABI/arch-arm"
417 make
HOST_CC=
"gcc -m32" CROSS=$NDKP
TARGET_FLAGS=
"$NDKF"
419 # Android/ARM, armeabi-v7a (ARMv7 VFP), Android
4.0+ (ICS)
422 NDKVER=$NDK/toolchains/arm-linux-androideabi-
4.6
423 NDKP=$NDKVER/prebuilt/linux-x86/bin/arm-linux-androideabi-
424 NDKF=
"--sysroot $NDK/platforms/android-$NDKABI/arch-arm"
425 NDKARCH=
"-march=armv7-a -mfloat-abi=softfp -Wl,--fix-cortex-a8"
426 make
HOST_CC=
"gcc -m32" CROSS=$NDKP
TARGET_FLAGS=
"$NDKF $NDKARCH"
428 # Android/MIPS, mips (MIPS32R1 hard-float), Android
4.0+ (ICS)
431 NDKVER=$NDK/toolchains/mipsel-linux-android-
4.6
432 NDKP=$NDKVER/prebuilt/linux-x86/bin/mipsel-linux-android-
433 NDKF=
"--sysroot $NDK/platforms/android-$NDKABI/arch-mips"
434 make
HOST_CC=
"gcc -m32" CROSS=$NDKP
TARGET_FLAGS=
"$NDKF"
436 # Android/x86, x86 (i686 SSE3), Android
4.0+ (ICS)
439 NDKVER=$NDK/toolchains/x86-
4.6
440 NDKP=$NDKVER/prebuilt/linux-x86/bin/i686-linux-android-
441 NDKF=
"--sysroot $NDK/platforms/android-$NDKABI/arch-x86"
442 make
HOST_CC=
"gcc -m32" CROSS=$NDKP
TARGET_FLAGS=
"$NDKF"
445 You can cross-compile for
<b id=
"ios">iOS
3.0+
</b> (iPhone/iPad) using the
<a href=
"http://developer.apple.com/devcenter/ios/index.action"><span class=
"ext">»</span> iOS SDK
</a>.
446 The environment variables need to match the iOS SDK version:
448 <p style=
"font-size: 8pt;">
449 Note:
<b>the JIT compiler is disabled for iOS
</b>, because regular iOS Apps
450 are not allowed to generate code at runtime. You'll only get the performance
451 of the LuaJIT interpreter on iOS. This is still faster than plain Lua, but
452 much slower than the JIT compiler. Please complain to Apple, not me.
456 IXCODE=`xcode-select -print-path`
457 ISDK=$IXCODE/Platforms/iPhoneOS.platform/Developer
458 ISDKVER=iPhoneOS6.0.sdk
460 ISDKF=
"-arch armv7 -isysroot $ISDK/SDKs/$ISDKVER"
461 make
HOST_CC=
"gcc -m32 -arch i386" CROSS=$ISDKP
TARGET_FLAGS=
"$ISDKF" \
465 <h3 id=
"consoles">Cross-compiling for consoles
</h3>
467 Building LuaJIT for consoles requires both a supported host compiler
468 (x86 or x64) and a cross-compiler (to PPC or ARM) from the official
472 Due to restrictions on consoles, the JIT compiler is disabled and only
473 the fast interpreter is built. This is still faster than plain Lua,
474 but much slower than the JIT compiler. The FFI is disabled, too, since
475 it's not very useful in such an environment.
478 The following commands build a static library
<tt>libluajit.a
</tt>,
479 which can be linked against your game, just like the Lua library.
482 To cross-compile for
<b id=
"ps3">PS3
</b> from a Linux host (requires
483 32 bit GCC, i.e. multilib Linux/x64) or a Windows host (requires
484 32 bit MinGW), run this command:
487 make
HOST_CC=
"gcc -m32" CROSS=ppu-lv2-
490 To cross-compile for
<b id=
"ps4">PS4
</b> from a Windows host,
491 open a
"Visual Studio .NET Command Prompt" (
64 bit host compiler),
492 <tt>cd
</tt> to the directory where you've unpacked the sources and
493 run the following commands:
500 To cross-compile for
<b id=
"psvita">PS Vita
</b> from a Windows host,
501 open a
"Visual Studio .NET Command Prompt" (
32 bit host compiler),
502 <tt>cd
</tt> to the directory where you've unpacked the sources and
503 run the following commands:
510 To cross-compile for
<b id=
"xbox360">Xbox
360</b> from a Windows host,
511 open a
"Visual Studio .NET Command Prompt" (
32 bit host compiler),
512 <tt>cd
</tt> to the directory where you've unpacked the sources and run
513 the following commands:
520 To cross-compile for
<b id=
"xboxone">Xbox One
</b> from a Windows host,
521 open a
"Visual Studio .NET Command Prompt" (
64 bit host compiler),
522 <tt>cd
</tt> to the directory where you've unpacked the sources and run
523 the following commands:
530 <h2 id=
"embed">Embedding LuaJIT
</h2>
532 LuaJIT is API-compatible with Lua
5.1. If you've already embedded Lua
533 into your application, you probably don't need to do anything to switch
534 to LuaJIT, except link with a different library:
537 <li>It's strongly suggested to build LuaJIT separately using the supplied
538 build system. Please do
<em>not
</em> attempt to integrate the individual
539 source files into your build tree. You'll most likely get the internal build
540 dependencies wrong or mess up the compiler flags. Treat LuaJIT like any
541 other external library and link your application with either the dynamic
542 or static library, depending on your needs.
</li>
543 <li>If you want to load C modules compiled for plain Lua
544 with
<tt>require()
</tt>, you need to make sure the public symbols
545 (e.g.
<tt>lua_pushnumber
</tt>) are exported, too:
546 <ul><li>On POSIX systems you can either link to the shared library
547 or link the static library into your application. In the latter case
548 you'll need to export all public symbols from your main executable
549 (e.g.
<tt>-Wl,-E
</tt> on Linux) and add the external dependencies
550 (e.g.
<tt>-lm -ldl
</tt> on Linux).
</li>
551 <li>Since Windows symbols are bound to a specific DLL name, you need to
552 link to the
<tt>lua51.dll
</tt> created by the LuaJIT build (do not rename
553 the DLL). You may link LuaJIT statically on Windows only if you don't
554 intend to load Lua/C modules at runtime.
558 If you're building a
64 bit application on OSX which links directly or
559 indirectly against LuaJIT, you need to link your main executable
562 -pagezero_size
10000 -image_base
100000000
564 Also, it's recommended to
<tt>rebase
</tt> all (self-compiled) shared libraries
565 which are loaded at runtime on OSX/x64 (e.g. C extension modules for Lua).
566 See:
<tt>man rebase
</tt>
569 <p>Additional hints for initializing LuaJIT using the C API functions:
</p>
572 <a href=
"http://lua-users.org/wiki/SimpleLuaApiExample"><span class=
"ext">»</span> simple example
</a>
573 for embedding Lua or LuaJIT into your application.
</li>
574 <li>Make sure you use
<tt>luaL_newstate
</tt>. Avoid using
575 <tt>lua_newstate
</tt>, since this uses the (slower) default memory
576 allocator from your system (no support for this on x64).
</li>
577 <li>Make sure you use
<tt>luaL_openlibs
</tt> and not the old Lua
5.0 style
578 of calling
<tt>luaopen_base
</tt> etc. directly.
</li>
579 <li>To change or extend the list of standard libraries to load, copy
580 <tt>src/lib_init.c
</tt> to your project and modify it accordingly.
581 Make sure the
<tt>jit
</tt> library is loaded or the JIT compiler
582 will not be activated.
</li>
583 <li>The
<tt>bit.*
</tt> module for bitwise operations
584 is already built-in. There's no need to statically link
585 <a href=
"http://bitop.luajit.org/"><span class=
"ext">»</span> Lua BitOp
</a> to your application.
</li>
588 <h2 id=
"distro">Hints for Distribution Maintainers
</h2>
590 The LuaJIT build system has extra provisions for the needs of most
591 POSIX-based distributions. If you're a package maintainer for
592 a distribution,
<em>please
</em> make use of these features and
593 avoid patching, subverting, autotoolizing or messing up the build system
597 There should be absolutely no need to patch
<tt>luaconf.h
</tt> or any
598 of the Makefiles. And please do not hand-pick files for your packages
—
599 simply use whatever
<tt>make install
</tt> creates. There's a reason
600 for all of the files
<em>and
</em> directories it creates.
603 The build system uses GNU make and auto-detects most settings based on
604 the host you're building it on. This should work fine for native builds,
605 even when sandboxed. You may need to pass some of the following flags to
606 <em>both
</em> the
<tt>make
</tt> and the
<tt>make install
</tt> command lines
607 for a regular distribution build:
610 <li><tt>PREFIX
</tt> overrides the installation path and should usually
611 be set to
<tt>/usr
</tt>. Setting this also changes the module paths and
612 the paths needed to locate the shared library.
</li>
613 <li><tt>DESTDIR
</tt> is an absolute path which allows you to install
614 to a shadow tree instead of the root tree of the build system.
</li>
615 <li><tt>MULTILIB
</tt> sets the architecture-specific library path component
616 for multilib systems. The default is
<tt>lib
</tt>.
</li>
617 <li>Have a look at the top-level
<tt>Makefile
</tt> and
<tt>src/Makefile
</tt>
618 for additional variables to tweak. The following variables
<em>may
</em> be
619 overridden, but it's
<em>not
</em> recommended, except for special needs
621 <tt>BUILDMODE, CC, HOST_CC, STATIC_CC, DYNAMIC_CC, CFLAGS, HOST_CFLAGS,
622 TARGET_CFLAGS, LDFLAGS, HOST_LDFLAGS, TARGET_LDFLAGS, TARGET_SHLDFLAGS,
623 TARGET_FLAGS, LIBS, HOST_LIBS, TARGET_LIBS, CROSS, HOST_SYS, TARGET_SYS
627 The build system has a special target for an amalgamated build, i.e.
628 <tt>make amalg
</tt>. This compiles the LuaJIT core as one huge C file
629 and allows GCC to generate faster and shorter code. Alas, this requires
630 lots of memory during the build. This may be a problem for some users,
631 that's why it's not enabled by default. But it shouldn't be a problem for
632 most build farms. It's recommended that binary distributions use this
633 target for their LuaJIT builds.
636 The tl;dr version of the above:
639 make amalg PREFIX=/usr && \
640 make install PREFIX=/usr DESTDIR=/tmp/buildroot
643 Finally, if you encounter any difficulties, please
644 <a href=
"contact.html">contact me
</a> first, instead of releasing a broken
645 package onto unsuspecting users. Because they'll usually gonna complain
646 to me (the upstream) and not you (the package maintainer), anyway.
652 Copyright
© 2005-
2015 Mike Pall
653 <span class=
"noprint">
655 <a href=
"contact.html">Contact
</a>