| Joakim Bech | 8e5c5b3 | 2018-10-25 08:18:32 +0200 | [diff] [blame] | 1 | .. _toolchains: |
| 2 | |
| 3 | ########## |
| 4 | Toolchains |
| 5 | ########## |
| 6 | OP-TEE uses both 32bit as well as 64bit toolchains and it is even possible to |
| 7 | mix them in some configurations. In theory you should be able to compile OP-TEE |
| 8 | with the Arm toolchains that are coming with your Linux distribution. But |
| 9 | instead of using those directly, we instead download the toolchains directly |
| 10 | from Arm. |
| 11 | |
| 12 | Download/install |
| 13 | **************** |
| 14 | We propose two ways to download the toolchains, both will put the toolchains |
| 15 | under the same path(s). |
| 16 | |
| 17 | 1. Direct download |
| 18 | ================== |
| 19 | Go the `Arm GCC download page`_ and download the "`AArch32 target with soft |
| 20 | float (arm-linux-gnueabi)`" for 32bit builds and the "`AArch64 GNU/Linux target |
| 21 | (aarch64-linux-gnu)`" for 64bit builds. When the downloads have finished, you |
| 22 | will untar them to a location that you later on will export to your ``$PATH``. |
| 23 | Here is an example |
| 24 | |
| 25 | .. code-block:: bash |
| 26 | |
| 27 | $ mkdir -p $HOME/toolchains |
| 28 | $ cd $HOME/toolchains |
| 29 | |
| 30 | # Download 32bit toolchain |
| 31 | $ wget https://developer.arm.com/-/media/Files/downloads/gnu-a/8.2-2019.01/gcc-arm-8.2-2019.01-x86_64-arm-linux-gnueabi.tar.xz |
| 32 | $ mkdir aarch32 |
| 33 | $ tar xf gcc-arm-8.2-2019.01-x86_64-arm-linux-gnueabi.tar.xz -C aarch32 --strip-components=1 |
| 34 | |
| 35 | # Download 64bit toolchain |
| 36 | $ wget https://developer.arm.com/-/media/Files/downloads/gnu-a/8.2-2019.01/gcc-arm-8.2-2019.01-x86_64-aarch64-linux-gnu.tar.xz |
| 37 | $ mkdir aarch64 |
| 38 | $ tar xf gcc-arm-8.2-2019.01-x86_64-aarch64-linux-gnu.tar.xz -C aarch64 --strip-components=1 |
| 39 | |
| 40 | 2. Using build.git |
| 41 | ================== |
| 42 | As an alternative, you can let :ref:`build`.git download them for you, but this |
| 43 | of course involves getting a git that you might not otherwise use. |
| 44 | |
| 45 | .. code-block:: bash |
| 46 | |
| 47 | $ cd $HOME |
| 48 | $ git clone https://github.com/OP-TEE/build.git |
| 49 | $ cd build |
| 50 | $ make -f toolchain.mk -j2 |
| 51 | |
| 52 | |
| 53 | Export PATH |
| 54 | *********** |
| 55 | If you have downloaded the toolchains as described above, you should have them |
| 56 | at ``$HOME/toolchains/{aarch32/aarch64}``, so now we just need to export the |
| 57 | paths and then you are ready to starting compiling OP-TEE components. |
| 58 | |
| 59 | .. code-block:: bash |
| 60 | |
| 61 | $ export PATH=$PATH:$HOME/toolchains/aarch32/bin:$HOME/toolchains/aarch64/bin |
| 62 | |
| 63 | .. _Arm GCC download page: https://developer.arm.com/open-source/gnu-toolchain/gnu-a/downloads |