Magic-Mirror/llvm-capstone
1
0
Fork 0
mirror of https://github.com/capstone-engine/llvm-capstone.git synced 2024-11-23 13:50:11 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

[docs] Rewrite/improve the docs for LLVM_NATIVE_TOOL_DIR

Browse Source 
Don't include it among the mandatory options; the automatically built
tools via a nested cmake build work fine these days
(in particular, since 93010544a8 /
https://reviews.llvm.org/D126313).

Clarify the directory path-to-host-bin into something more verbose,
to avoid ambiguity with LLVM_HOST_TRIPLE.

Differential Revision: https://reviews.llvm.org/D142960
This commit is contained in:
Martin Storsjö 2023-01-31 11:09:50 +02:00
parent cb19e3b20d
commit 4cda8e6267
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
llvm/docs/HowToCrossCompileLLVM.rst
View File

@ -42,7 +42,6 @@ The CMake options you need to add are:
* ``-DCMAKE_SYSTEM_NAME=<target-system>``
* ``-DCMAKE_INSTALL_PREFIX=<install-dir>``
* ``-DLLVM_NATIVE_TOOL_DIR=<path-to-host-bin>``
* ``-DLLVM_HOST_TRIPLE=arm-linux-gnueabihf``
* ``-DLLVM_TARGETS_TO_BUILD=ARM``
@ -69,10 +68,13 @@ In addition to the ones above, you'll also need:
* Appropriate use of ``-I`` and ``-L``, depending on how the cross GCC is installed,
and where are the libraries and headers.
The ``LLVM_NATIVE_TOOL_DIR`` option allows you to reuse prebuilt binaries
(``llvm-tblgen``, ``clang-tblgen`` etc) for the build host, if such are
available. If that's not available, the LLVM cross build will automatically
launch a nested build to build the tools that are required.
You may also want to set the ``LLVM_NATIVE_TOOL_DIR`` option - pointing
at a directory with prebuilt LLVM tools (``llvm-tblgen``, ``clang-tblgen``
etc) for the build host, allowing you to them reuse them if available.
E.g. ``-DLLVM_NATIVE_TOOL_DIR=<path-to-native-llvm-build>/bin``.
If the option isn't set (or the directory doesn't contain all needed tools),
the LLVM cross build will automatically launch a nested build to build the
tools that are required.
The CXX flags define the target, cpu (which in this case
defaults to ``fpu=VFP3`` with NEON), and forcing the hard-float ABI. If you're