1 # How to Cross-build Runtime for AARCH64
3 In **ONE**, we use `AARCH64` on build files such as Makefile, CMakeLists.txt and so on.
5 ## Prepare AARCH64 Ubuntu RootFS
7 Install required packages
10 $ sudo apt-get install qemu qemu-user-static binfmt-support debootstrap
13 Use `install_rootfs.sh` script to prepare Root File System. You should have `sudo`
16 $ sudo ./tools/cross/install_rootfs.sh aarch64
18 - supports `arm`(default) and `aarch64` architecutre for now
19 - supports `xenial`(default), `trusty` and `bionic` release
23 $ ./tools/cross/install_rootfs.sh -h
26 RootFS will be prepared at `tools/cross/rootfs/aarch64` folder.
28 ***\* CAUTION: The OS version of rootfs must match the OS version of execution target device. On the other hand, you need to match the Ubuntu version of the development PC with the Ubuntu version of rootfs to be used for cross-build. Otherwise, unexpected build errors may occur.***
30 If you are using Ubuntu 16.04 LTS, select `xenial`, if you are using Ubuntu 18.04 LTS, select `bionic`. You can check your Ubuntu code name in the following way.
33 $ cat /etc/lsb-release
36 DISTRIB_CODENAME=bionic
37 DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS"
40 If a build error occurs because the version of the development system and the target system do not match, and if you can't replace your development system for any reason, you can consider [cross-build using the docker image](how-to-build-runtime-using-prebuilt-docker-image.md).
42 ### Prepare RootFS at alternative folder
44 Use `ROOTFS_DIR` to a full path to prepare at alternative path.
47 $ ROOTFS_DIR=/home/user/rootfs/aarch64-xenial sudo -E ./tools/cross/install_rootfs.sh aarch64
52 If you need to use proxy server while building the rootfs, use `--setproxy` option.
56 $ sudo ./tools/cross/install_rootfs.sh aarch64 --setproxy="1.2.3.4:8080"
58 $ sudo ./tools/cross/install_rootfs.sh aarch64 --setproxy="proxy.server.com:8888"
61 This will put `apt` proxy settings in `rootfs/etc/apt/apt.conf.d/90proxy` file
62 for `http`, `https` and `ftp` protocol.
64 ## Cross build for AARCH64
66 Install cross compilers
68 $ sudo apt-get install gcc-aarch64-linux-gnu g++-aarch64-linux-gnu
71 Give `TARGET_ARCH` variable to set the target architecture
73 $ CROSS_BUILD=1 TARGET_ARCH=aarch64 make
74 $ CROSS_BUILD=1 TARGET_ARCH=aarch64 make install
76 - supports `armv7l` and `aarch64` for now
78 If you used `ROOTFS_DIR` to prepare in alternative folder,
79 you should also give this to makefile.
81 $ CROSS_BUILD=1 ROOTFS_DIR=/home/user/rootfs/aarch64-xenial TARGET_ARCH=aarch64 make
82 $ CROSS_BUILD=1 ROOTFS_DIR=/home/user/rootfs/aarch64-xenial TARGET_ARCH=aarch64 make install
84 You can also omit the `CROSS_BUILD=1` option if you explicitly pass `ROOTFS_DIR`. In that case, if
85 the `TARGET_ARCH` are differs from the hostarchitecture, the make script automatically applies
86 `CROSS_BUILD=1`. So, if you set `ROOTFS_DIR` as an environment variable, you can simply perform
87 normal build and cross build as follows.
90 $ export ROOTFS_DIR=xxx
92 $ make all install # do normal build
93 $ TARGET_ARCH=aarch64 make all install # do cross build
98 To run and test the cross-compiled runtime, you need to copy the compiled output to the target device of the architecture in which it is executable. Please refer to the following document for details on the test procedure. In the guide, `armv7l-linux.debug` in path should be replaced by referring to your build result.
100 - [Testing neural network model inference with a cross-build runtime](./how-to-cross-build-runtime-for-arm.md#run-test)