Install required packages
$ sudo apt-get install qemu-user-static binfmt-support debootstrap
Use install_rootfs.sh
script to prepare Root File System. You should have sudo
$ sudo ./tools/cross/install_rootfs.sh arm
- supports
arm
(default) andaarch64
architecutre for now - supports
focal
,jammy
, andnoble
release
To see the options,
$ ./tools/cross/install_rootfs.sh -h
RootFS will be prepared at tools/cross/rootfs/arm
or tools/cross/rootfs/aarch64
folder.
* 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.
If you are using Ubuntu 20.04 LTS, select focal
, if you are using Ubuntu 22.04 LTS, select jammy
. You can check your Ubuntu code name in the following way.
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS"
install_rootfs.sh
will select development system code name as default.
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.
Use ROOTFS_DIR
to a full path to prepare at alternative path.
$ ROOTFS_DIR=/home/user/rootfs/arm-bionic sudo -E ./tools/cross/install_rootfs.sh arm
If you need to use proxy server while building the rootfs, use --setproxy
option.
# for example,
$ sudo ./tools/cross/install_rootfs.sh arm --setproxy="1.2.3.4:8080"
# or
$ sudo ./tools/cross/install_rootfs.sh arm --setproxy="proxy.server.com:8888"
This will put apt
proxy settings in rootfs/etc/apt/apt.conf.d/90proxy
file
for http
, https
and ftp
protocol.
We recommend you have g++ >= 6.1 installed on your system because NN generated tests require it (c++14).
On Ubuntu 20.04 LTS, you can install using apt-get
.
Choose g++ version whatever you prefer: 9 (default) or 10. We are officially testing on default g++ version, so we don't confirm build on different version.
$ sudo apt-get install g++-{9,10}-arm-linux-gnueabihf
If you select specific version, update symbolic link for build toolchain.
Otherwise, you should set your custom cmake crossbuild toolchain. You can find cmake toolchain files in infra/nnfw/cmake/buildtool/cross/
.
$ update-alternatives --install /usr/bin/arm-linux-gnueabihf-gcc arm-linux-gnueabihf-gcc /usr/bin/arm-linux-gnueabihf-gcc-10 80 \
--slave /usr/bin/arm-linux-gnueabihf-g++ arm-linux-gnueabihf-g++ /usr/bin/arm-linux-gnueabihf-g++-10 \
--slave /usr/bin/arm-linux-gnueabihf-gcov arm-linux-gnueabihf-gcov /usr/bin/arm-linux-gnueabihf-gcov-10
Same with Ubuntu 20.04 LTS. (except g++ version)
Mostly you only need once of ACL (ARM Compute Library) build.
To build ACL, you need to install scons
$ sudo apt-get install scons
ACL source will be automatically installed in externals/ARMCOMPUTE
when you build runtime without any changes.
You can check ACL source information in infra/cmake/packages/ARMComputeSourceConfig.cmake
Give TARGET_ARCH
variable to set the target architecture.
If you used ROOTFS_DIR
to prepare in alternative folder, you should also give this to makefile.
$ CROSS_BUILD=1 TARGET_ARCH=armv7l make -f Makefile.template
# If ROOTFS_DIR is in alternative folder
$ ROOTFS_DIR=/path/to/your/rootfs/arm \
CROSS_BUILD=1 TARGET_ARCH=armv7l make
You can also omit the CROSS_BUILD=1
option if you explicitly pass ROOTFS_DIR
. In that case, if
the TARGET_ARCH
are differs from the hostarchitecture, the make script automatically applies
CROSS_BUILD=1
. So, if you set ROOTFS_DIR
as an environment variable, you can simply perform
normal build and cross build as follows.
$ export ROOTFS_DIR=xxx
...
$ make -f Makefile.template # do normal build
$ TARGET_ARCH=armv7l make -f Makefile.template # do cross build
Makefile.template will pass crossbuild toolchain setting to cmake automatically by parsing variables.
To run and test the cross-compiled runtime, you need to install library packages and copy the compiled output to the target device of the architecture in which it is executable.
- Install hdf5 library package
$ sudo apt install libhdf5-dev
- Copy all artifacts under the
./Product/armv7l-linux.<BUILD_TYPE>
folder to the target device, Odroid-XU4 for example, as a whole.
$ ssh odroid mkdir -p one/Product
sjlee@odroid's password:
$ scp -rp ./Product/armv7l-linux.debug odroid:one/Product
sjlee@odroid's password:
FillFrom_runner 100% 224KB 223.6KB/s 00:00
benchmark_nnapi.sh 100% 7464 7.3KB/s 00:00
common.sh 100% 2084 2.0KB/s 00:00
test_framework.sh 100% 3154 3.1KB/s 00:00
test-driver.sh
...
- Log in to the target device, go to the copied path, and reestore the symbolic link settings of the
Product
directory.
$ ssh odroid
sjlee@odroid's password:
...
$ cd ~/one/Product
$ ln ${PWD}/armv7l-linux.debug/out out
$ cd ..
$ ls -la Product
drwxrwxr-x 5 sjlee sjlee 4096 Jun 4 20:55 armv7l-linux.debug
lrwxrwxrwx 1 sjlee sjlee 51 Jun 4 20:55 out -> /home/sjlee/one/Product/armv7l-linux.debug/out
Now you can test the compilation result in the same way as the native build. Please refer to the following document for details on the test procedure.