<div dir="ltr">Thanks Sean!t</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 9 September 2013 20:05, Sean Silva <span dir="ltr"><<a href="mailto:silvas@purdue.edu" target="_blank">silvas@purdue.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Author: silvas<br>
Date: Mon Sep 9 14:05:03 2013<br>
New Revision: 190324<br>
<br>
URL: <a href="http://llvm.org/viewvc/llvm-project?rev=190324&view=rev" target="_blank">http://llvm.org/viewvc/llvm-project?rev=190324&view=rev</a><br>
Log:<br>
[docs] Some typographical fixes.<br>
<br>
Modified:<br>
llvm/trunk/docs/HowToCrossCompileLLVM.rst<br>
<br>
Modified: llvm/trunk/docs/HowToCrossCompileLLVM.rst<br>
URL: <a href="http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/HowToCrossCompileLLVM.rst?rev=190324&r1=190323&r2=190324&view=diff" target="_blank">http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/HowToCrossCompileLLVM.rst?rev=190324&r1=190323&r2=190324&view=diff</a><br>
==============================================================================<br>
--- llvm/trunk/docs/HowToCrossCompileLLVM.rst (original)<br>
+++ llvm/trunk/docs/HowToCrossCompileLLVM.rst Mon Sep 9 14:05:03 2013<br>
@@ -22,15 +22,15 @@ nowadays) to a hard-float ARM target (mo<br>
<br>
The packages you'll need are:<br>
<br>
- * cmake<br>
- * ninja-build (from backports in Ubuntu)<br>
- * gcc-4.7-arm-linux-gnueabihf<br>
- * gcc-4.7-multilib-arm-linux-gnueabihf<br>
- * binutils-arm-linux-gnueabihf<br>
- * libgcc1-armhf-cross<br>
- * libsfgcc1-armhf-cross<br>
- * libstdc++6-armhf-cross<br>
- * libstdc++6-4.7-dev-armhf-cross<br>
+ * ``cmake``<br>
+ * ``ninja-build`` (from backports in Ubuntu)<br>
+ * ``gcc-4.7-arm-linux-gnueabihf``<br>
+ * ``gcc-4.7-multilib-arm-linux-gnueabihf``<br>
+ * ``binutils-arm-linux-gnueabihf``<br>
+ * ``libgcc1-armhf-cross``<br>
+ * ``libsfgcc1-armhf-cross``<br>
+ * ``libstdc++6-armhf-cross``<br>
+ * ``libstdc++6-4.7-dev-armhf-cross``<br>
<br>
Configuring CMake<br>
-----------------<br>
@@ -39,32 +39,29 @@ For more information on how to configure<br>
see :doc:`CMake`.<br>
<br>
The CMake options you need to add are:<br>
- * -DCMAKE_CROSSCOMPILING=True<br>
- * -DCMAKE_INSTALL_PREFIX=<install-dir><br>
- * -DLLVM_TABLEGEN=<path-to-host-bin>/llvm-tblgen<br>
- * -DCLANG_TABLEGEN=<path-to-host-bin>/clang-tblgen<br>
- * -DLLVM_DEFAULT_TARGET_TRIPLE=arm-linux-gnueabihf<br>
- * -DLLVM_TARGET_ARCH=ARM<br>
- * -DLLVM_TARGETS_TO_BUILD=ARM<br>
- * -DCMAKE_CXX_FLAGS='-target armv7a-linux-gnueabihf -mcpu=cortex-a9<br>
- -I/usr/arm-linux-gnueabihf/include/c++/4.7.2/arm-linux-gnueabihf/<br>
- -I/usr/arm-linux-gnueabihf/include/ -mfloat-abi=hard<br>
- -ccc-gcc-name arm-linux-gnueabihf-gcc'<br>
+ * ``-DCMAKE_CROSSCOMPILING=True``<br>
+ * ``-DCMAKE_INSTALL_PREFIX=<install-dir>``<br>
+ * ``-DLLVM_TABLEGEN=<path-to-host-bin>/llvm-tblgen``<br>
+ * ``-DCLANG_TABLEGEN=<path-to-host-bin>/clang-tblgen``<br>
+ * ``-DLLVM_DEFAULT_TARGET_TRIPLE=arm-linux-gnueabihf``<br>
+ * ``-DLLVM_TARGET_ARCH=ARM``<br>
+ * ``-DLLVM_TARGETS_TO_BUILD=ARM``<br>
+ * ``-DCMAKE_CXX_FLAGS='-target armv7a-linux-gnueabihf -mcpu=cortex-a9 -I/usr/arm-linux-gnueabihf/include/c++/4.7.2/arm-linux-gnueabihf/ -I/usr/arm-linux-gnueabihf/include/ -mfloat-abi=hard -ccc-gcc-name arm-linux-gnueabihf-gcc'``<br>
<br>
The TableGen options are required to compile it with the host compiler,<br>
-so you'll need to compile LLVM (or at least `llvm-tblgen`) to your host<br>
+so you'll need to compile LLVM (or at least ``llvm-tblgen``) to your host<br>
platform before you start. The CXX flags define the target, cpu (which<br>
-defaults to fpu=VFP3 with NEON), and forcing the hard-float ABI. If you're<br>
+defaults to ``fpu=VFP3`` with NEON), and forcing the hard-float ABI. If you're<br>
using Clang as a cross-compiler, you will *also* have to set ``-ccc-gcc-name``,<br>
to make sure it picks the correct linker.<br>
<br>
Most of the time, what you want is to have a native compiler to the<br>
platform itself, but not others. It might not even be feasible to<br>
produce x86 binaries from ARM targets, so there's no point in compiling<br>
-all back-ends. For that reason, you should also set the "TARGETS_TO_BUILD"<br>
-to only build the ARM back-end.<br>
+all back-ends. For that reason, you should also set the<br>
+``TARGETS_TO_BUILD`` to only build the ARM back-end.<br>
<br>
-You must set the CMAKE_INSTALL_PREFIX, otherwise a ``ninja install``<br>
+You must set the ``CMAKE_INSTALL_PREFIX``, otherwise a ``ninja install``<br>
will copy ARM binaries to your root filesystem, which is not what you<br>
want.<br>
<br>
@@ -76,7 +73,7 @@ running CMake:<br>
<br>
#. If you're using Clang as the cross-compiler, there is a problem in<br>
the LLVM ARM back-end that is producing absolute relocations on<br>
- position-independent code (R_ARM_THM_MOVW_ABS_NC), so for now, you<br>
+ position-independent code (``R_ARM_THM_MOVW_ABS_NC``), so for now, you<br>
should disable PIC:<br>
<br>
.. code-block:: bash<br>
@@ -88,25 +85,25 @@ running CMake:<br>
<br>
#. The ARM libraries won't be installed in your system, and possibly<br>
not easily installable anyway, so you'll have to build/download<br>
- them separately. But the CMake prepare step, which check for<br>
- dependencies, will check the `host` libraries, not the `target`<br>
+ them separately. But the CMake prepare step, which checks for<br>
+ dependencies, will check the *host* libraries, not the *target*<br>
ones.<br>
<br>
A quick way of getting the libraries is to download them from<br>
a distribution repository, like Debian (<a href="http://packages.debian.org/wheezy/" target="_blank">http://packages.debian.org/wheezy/</a>),<br>
- and download the missing libraries. Note that the `libXXX`<br>
- will have the shared objects (.so) and the `libXXX-dev` will<br>
- give you the headers and the static (.a) library. Just in<br>
+ and download the missing libraries. Note that the ``libXXX``<br>
+ will have the shared objects (``.so``) and the ``libXXX-dev`` will<br>
+ give you the headers and the static (``.a``) library. Just in<br>
case, download both.<br>
<br>
The ones you need for ARM are: ``libtinfo``, ``zlib1g``,<br>
``libxml2`` and ``liblzma``. In the Debian repository you'll<br>
find downloads for all architectures.<br>
<br>
- After you download and unpack all `.deb` packages, copy all<br>
+ After you download and unpack all ``.deb`` packages, copy all<br>
``.so`` and ``.a`` to a directory, make the appropriate<br>
symbolic links (if necessary), and add the relevant ``-L``<br>
- and ``-I`` paths to -DCMAKE_CXX_FLAGS above.<br>
+ and ``-I`` paths to ``-DCMAKE_CXX_FLAGS`` above.<br>
<br>
<br>
Running CMake and Building<br>
@@ -124,9 +121,9 @@ If you're using Clang as the cross-compi<br>
<br>
$ CC='clang' CXX='clang++' cmake -G Ninja <source-dir> <options above><br>
<br>
-If you have clang/clang++ on the path, it should just work, and special<br>
+If you have ``clang``/``clang++`` on the path, it should just work, and special<br>
Ninja files will be created in the build directory. I strongly suggest<br>
-you to run cmake on a separate build directory, *not* inside the<br>
+you to run ``cmake`` on a separate build directory, *not* inside the<br>
source tree.<br>
<br>
To build, simply type:<br>
@@ -151,7 +148,7 @@ via:<br>
<br>
$ ninja install<br>
<br>
-which will create a sysroot on the install-dir. You can then TarGz<br>
+which will create a sysroot on the install-dir. You can then tar<br>
that directory into a binary with the full triple name (for easy<br>
identification), like:<br>
<br>
@@ -160,9 +157,9 @@ identification), like:<br>
$ ln -sf <install-dir> arm-linux-gnueabihf-clang<br>
$ tar zchf arm-linux-gnueabihf-clang.tar.gz arm-linux-gnueabihf-clang<br>
<br>
-If you copy that TarBall to your target board, you'll be able to use<br>
+If you copy that tarball to your target board, you'll be able to use<br>
it for running the test-suite, for example. Follow the guidelines at<br>
-<a href="http://llvm.org/docs/lnt/quickstart.html" target="_blank">http://llvm.org/docs/lnt/quickstart.html</a>, unpack the TarBall in the<br>
+<a href="http://llvm.org/docs/lnt/quickstart.html" target="_blank">http://llvm.org/docs/lnt/quickstart.html</a>, unpack the tarball in the<br>
test directory, and use options:<br>
<br>
.. code-block:: bash<br>
<br>
<br>
_______________________________________________<br>
llvm-commits mailing list<br>
<a href="mailto:llvm-commits@cs.uiuc.edu">llvm-commits@cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits</a><br>
</blockquote></div><br></div>