OpenHarmony/third_party_mesa3d
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: Update llvmpipe docs.

Browse Source 
Recommend LLVM 2.9, it has been working quite well, and unlike earlier
versions, it works out-of-the-box without patches.

Update Windows instructions.
This commit is contained in:
José Fonseca
2011-11-05 10:38:16 +00:00
parent 95ef069e1c
commit 65d0c840b0
1 changed files with 23 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

48
docs/llvmpipe.html
View File

@@ -22,21 +22,20 @@ It's the fastest software rasterizer for Mesa.
<h1>Requirements</h1> <h1>Requirements</h1>
<dl> <ul>
<dt>An x86 or amd64 processor. 64-bit mode is preferred.</dt> <li>
<dd> <p>An x86 or amd64 processor; 64-bit mode recommended.</p
<p> <p>
Support for sse2 is strongly encouraged. Support for ssse3, and sse4.1 will Support for SSE2 is strongly encouraged. Support for SSSE3, and SSE4.1 will
yield the most efficient code. The less features the CPU has the more yield the most efficient code. The less features the CPU has the more
likely is that you ran into underperforming, buggy, or incomplete code. likely is that you ran into underperforming, buggy, or incomplete code.
</p> </p>
<p> <p>
See /proc/cpuinfo to know what your CPU supports. See /proc/cpuinfo to know what your CPU supports.
</p> </p>
</dd> </li>
<dt>LLVM. Version 2.8 recommended. 2.6 or later required.</dt> <li>
<dd> <p>LLVM: version 2.9 recommended; 2.6 or later required.</p>
<p>
<b>NOTE</b>: LLVM 2.8 and earlier will not work on systems that support the <b>NOTE</b>: LLVM 2.8 and earlier will not work on systems that support the
Intel AVX extensions (e.g. Sandybridge). LLVM's code generator will Intel AVX extensions (e.g. Sandybridge). LLVM's code generator will
fail when trying to emit AVX instructions. This was fixed in LLVM 2.9. fail when trying to emit AVX instructions. This was fixed in LLVM 2.9.
@@ -54,26 +53,25 @@ It's the fastest software rasterizer for Mesa.
</pre> </pre>
<p> <p>
For Windows download pre-built MSVC 9.0 or MinGW binaries from For Windows you will need to build LLVM from source with MSVC or MINGW
http://people.freedesktop.org/~jrfonseca/llvm/ and set the LLVM environment (either natively or through cross compilers) and CMake, and set the LLVM
variable to the extracted path. environment variable to the directory you installed it to.
</p>
<p> LLVM will be statically linked, so when building on MSVC it needs to be
For MSVC there are two set of binaries: llvm-x.x-msvc32mt.7z and built with a matching CRT as Mesa, and you'll need to pass
llvm-x.x-msvc32mtd.7z . -DLLVM_USE_CRT_RELEASE=MTd for debug and checked builds,
</p> -DLLVM_USE_CRT_RELEASE=MTd for profile and release builds.
<p> You can build only the x86 target by passing -DLLVM_TARGETS_TO_BUILD=X86
You have to set the LLVM=/path/to/llvm-x.x-msvc32mtd env var when passing to cmake.
debug=yes to scons, and LLVM=/path/to/llvm-x.x-msvc32mt when building with
debug=no. This is necessary as LLVM builds as static library so the chosen
MS CRT must match.
</p> </p>
</dd> </li>
<li>
<p>scons (optional)</p>
</li>
</ul>
<dt>scons (optional)</dt>
</dl>
@@ -93,7 +91,7 @@ Alternatively, you can build it with GNU make, if you prefer, by invoking it as
but the rest of these instructions assume that scons is used. but the rest of these instructions assume that scons is used.
For windows is everything the except except the winsys: For Windows the procedure is similar except the target:
<pre> <pre>
scons build=debug libgl-gdi scons build=debug libgl-gdi