diff options
| author | Mike Pall <mike> | 2010-01-17 22:02:13 +0100 |
|---|---|---|
| committer | Mike Pall <mike> | 2010-01-17 22:02:13 +0100 |
| commit | 379b8c5fe4cc2a2872c0d7f88cbc2a44d8097246 (patch) | |
| tree | 5a3a10dc9bba41df9b05ca3db005d214cb09c07f /doc/install.html | |
| parent | 4b0725d5fc87da33477b13e74a32f24fafda3541 (diff) | |
| download | luajit-379b8c5fe4cc2a2872c0d7f88cbc2a44d8097246.tar.gz luajit-379b8c5fe4cc2a2872c0d7f88cbc2a44d8097246.tar.bz2 luajit-379b8c5fe4cc2a2872c0d7f88cbc2a44d8097246.zip | |
Update docs with x64 build instructions.
Diffstat (limited to 'doc/install.html')
| -rw-r--r-- | doc/install.html | 62 |
1 files changed, 57 insertions, 5 deletions
diff --git a/doc/install.html b/doc/install.html index faa60770..605f954d 100644 --- a/doc/install.html +++ b/doc/install.html | |||
| @@ -54,6 +54,17 @@ LuaJIT currently builds out-of-the box on all popular x86 systems | |||
| 54 | (Linux, Windows, OSX etc.). It builds and runs fine as a 32 bit | 54 | (Linux, Windows, OSX etc.). It builds and runs fine as a 32 bit |
| 55 | application under x64-based systems, too. | 55 | application under x64-based systems, too. |
| 56 | </p> | 56 | </p> |
| 57 | <p class="indent" style="color: #00a000;"> | ||
| 58 | The x64 port of LuaJIT is still experimental and not enabled by default. | ||
| 59 | It only contains the interpreter and only builds on Linux/x64 and WIN64 | ||
| 60 | right now. If you want to give it a try, follow the special build instructions | ||
| 61 | below. | ||
| 62 | </p> | ||
| 63 | <p class="indent" style="color: #00a000;"> | ||
| 64 | Note that the pure interpreter is quite a bit faster than Lua, but of | ||
| 65 | course not as fast as the x86 JIT compiler. Work on the x64 JIT compiler | ||
| 66 | is still ongoing. | ||
| 67 | </p> | ||
| 57 | 68 | ||
| 58 | <h2>Configuring LuaJIT</h2> | 69 | <h2>Configuring LuaJIT</h2> |
| 59 | <p> | 70 | <p> |
| @@ -84,8 +95,8 @@ complete SDK. | |||
| 84 | </p> | 95 | </p> |
| 85 | <p> | 96 | <p> |
| 86 | E.g. on a current Debian/Ubuntu, install <tt>libc6-dev</tt> | 97 | E.g. on a current Debian/Ubuntu, install <tt>libc6-dev</tt> |
| 87 | with the package manager. Currently LuaJIT only builds as a 32 bit | 98 | with the package manager. Currently LuaJIT builds as a 32 bit |
| 88 | application, so you actually need to install <tt>libc6-dev-i386</tt> | 99 | application by default, so you actually need to install <tt>libc6-dev-i386</tt> |
| 89 | when building on an x64 OS. | 100 | when building on an x64 OS. |
| 90 | </p> | 101 | </p> |
| 91 | <p> | 102 | <p> |
| @@ -106,6 +117,15 @@ which is probably the default on your system, anyway. Simply run: | |||
| 106 | <pre class="code"> | 117 | <pre class="code"> |
| 107 | make | 118 | make |
| 108 | </pre> | 119 | </pre> |
| 120 | <div style="color: #00a000;"> | ||
| 121 | <p> | ||
| 122 | You can force a build of the x64 interpreter on Linux/x64 with the | ||
| 123 | following command: | ||
| 124 | </p> | ||
| 125 | <pre class="code"> | ||
| 126 | make CC="gcc -m64" | ||
| 127 | </pre> | ||
| 128 | </div> | ||
| 109 | <p> | 129 | <p> |
| 110 | By default modules are only searched under the prefix <tt>/usr/local</tt>. | 130 | By default modules are only searched under the prefix <tt>/usr/local</tt>. |
| 111 | You can add an extra prefix to the search paths by appending the | 131 | You can add an extra prefix to the search paths by appending the |
| @@ -122,7 +142,7 @@ in <tt>src/Makefile</tt>. Change it, if you want to build on an older version. | |||
| 122 | <p> | 142 | <p> |
| 123 | The top-level Makefile installs LuaJIT by default under | 143 | The top-level Makefile installs LuaJIT by default under |
| 124 | <tt>/usr/local</tt>, i.e. the executable ends up in | 144 | <tt>/usr/local</tt>, i.e. the executable ends up in |
| 125 | <tt>/usr/local/bin</tt> and so on. You need to have root privileges | 145 | <tt>/usr/local/bin</tt> and so on. You need root privileges |
| 126 | to write to this path. So, assuming sudo is installed on your system, | 146 | to write to this path. So, assuming sudo is installed on your system, |
| 127 | run the following command and enter your sudo password: | 147 | run the following command and enter your sudo password: |
| 128 | </p> | 148 | </p> |
| @@ -157,9 +177,15 @@ Either install one of the open source SDKs | |||
| 157 | GCC plus the required development headers. | 177 | GCC plus the required development headers. |
| 158 | </p> | 178 | </p> |
| 159 | <p> | 179 | <p> |
| 160 | Or install Microsoft's Visual C++ (MSVC) — the freely downloadable | 180 | Or install Microsoft's Visual C++ (MSVC). The freely downloadable |
| 161 | <a href="http://www.microsoft.com/Express/VC/"><span class="ext">»</span> Express Edition</a> | 181 | <a href="http://www.microsoft.com/Express/VC/"><span class="ext">»</span> Express Edition</a> |
| 162 | works just fine. | 182 | works just fine, but only contains an x86 compiler. |
| 183 | </p> | ||
| 184 | <p> | ||
| 185 | The freely downloadable | ||
| 186 | <a href="http://msdn.microsoft.com/en-us/windowsserver/bb980924.aspx"><span class="ext">»</span> Windows SDK</a> | ||
| 187 | only comes with command line tools, but this is all you need to build LuaJIT. | ||
| 188 | It contains x86 and x64 compilers. | ||
| 163 | </p> | 189 | </p> |
| 164 | <p> | 190 | <p> |
| 165 | Next, download the source package and unpack it using an archive manager | 191 | Next, download the source package and unpack it using an archive manager |
| @@ -177,6 +203,32 @@ msvcbuild | |||
| 177 | <p> | 203 | <p> |
| 178 | Then follow the installation instructions below. | 204 | Then follow the installation instructions below. |
| 179 | </p> | 205 | </p> |
| 206 | <h3>Building with the Windows SDK</h3> | ||
| 207 | <p> | ||
| 208 | Open a "Windows SDK Command Shell" and select the x86 compiler: | ||
| 209 | </p> | ||
| 210 | <pre class="code"> | ||
| 211 | setenv /release /x86 | ||
| 212 | </pre> | ||
| 213 | <div style="color: #00a000;"> | ||
| 214 | <p> | ||
| 215 | Or select the x64 compiler (this only builds the interpreter right now): | ||
| 216 | </p> | ||
| 217 | <pre class="code"> | ||
| 218 | setenv /release /x64 | ||
| 219 | </pre> | ||
| 220 | </div> | ||
| 221 | <p> | ||
| 222 | Then <tt>cd</tt> to the directory where you've unpacked the sources | ||
| 223 | and run these commands: | ||
| 224 | </p> | ||
| 225 | <pre class="code"> | ||
| 226 | cd src | ||
| 227 | msvcbuild | ||
| 228 | </pre> | ||
| 229 | <p> | ||
| 230 | Then follow the installation instructions below. | ||
| 231 | </p> | ||
| 180 | <h3>Building with MinGW or Cygwin</h3> | 232 | <h3>Building with MinGW or Cygwin</h3> |
| 181 | <p> | 233 | <p> |
| 182 | Open a command prompt window and make sure the MinGW or Cygwin programs | 234 | Open a command prompt window and make sure the MinGW or Cygwin programs |
