diff options
| author | Mike Kelly <mike.kelly@arm.com> | 2020-03-04 16:49:19 +0000 |
|---|---|---|
| committer | Jim Flynn <jim.flynn@arm.com> | 2020-03-09 16:44:22 +0000 |
| commit | 9ada14e98d99d965bfa98fff1cfb9fde91a744fd (patch) | |
| tree | e636041d99ad8cfe024c8ad61aba77b637e0f454 | |
| parent | ec1e5b8d0a0eeba7eae0f1fdb5e32c72f8a8093c (diff) | |
| download | android-nn-driver-9ada14e98d99d965bfa98fff1cfb9fde91a744fd.tar.gz | |
MLCE-149 Build problems
* Updated FAQ to better explain how to resolve build problems due to missing or mismatched versions of boost, clframework and armnn
Signed-off-by: Mike Kelly <mike.kelly@arm.com>
Change-Id: I115e075e9160d01d400cc53fc4d3f7fc788f3b50
| -rw-r--r-- | docs/FAQ.md | 17 |
1 files changed, 14 insertions, 3 deletions
diff --git a/docs/FAQ.md b/docs/FAQ.md index e62bf540..5e5c3728 100644 --- a/docs/FAQ.md +++ b/docs/FAQ.md @@ -20,12 +20,19 @@ An acceptable workaround is to increase the timeout defined in AndroidTest.xml, Problems seen when trying to build the android-nn-driver obtained from GitHub ----------------------------------------------------------------------------- -Some users have encountered difficulties when attempting to build copies of the android-nn-driver obtained from GitHub. The build reports missing module source paths from clframework or armnn. This is due to incompatiblities between the android-nn-driver and armnn or clframework versions. The versions of android-nn-driver, armnn and clframework have to match for them to work together. So the 19.08 version of android-nn-driver, clframework and armnn will work together but none of them will work with earlier or later versions of the others. In order to ensure that the correct versions of armnn or clframework are obtained you can do the following: +Some users have encountered difficulties when attempting to build copies of the android-nn-driver obtained from GitHub. The build reports missing module source paths from boost_1_64_0, clframework or armnn. These errors can look like this: -1. Delete or move the armnn or clframework directories from the android-nn-driver directory. +'error: vendor/arm/android-nn-driver/Android.bp:892:1: module "libboost_program_options" variant "android_arm_variant": module source path "vendor/arm/android-nn-driver/boost_1_64_0" does not exist' +'error: vendor/arm/android-nn-driver/Android.bp:45:1: variant "android_arm64_armv7": module "armnn-arm_compute" "module source path "vendor/arm/android-nn-driver/clframework/build/android-arm64v8a/src/core/CL" does not exist' + +These errors are due to missing dependencies or incompatiblities between the android-nn-driver and armnn or clframework versions. The android-nn-driver requires boost_1_40_0 to build. The versions of android-nn-driver, armnn and clframework will have to match for them to work together. So the 19.08 version of android-nn-driver, clframework and armnn will work together but none of them will work with earlier or later versions of the others. + +In order to ensure that the correct versions of boost, armnn and the clframework are obtained you can do the following: + +1. Delete or move any boost, armnn or clframework directories from the android-nn-driver directory. 2. Run the setup.sh script in the android-nn-driver directory. -This will download the correct versions from GitHub and the android-nn-driver should build correctly. Alternatively you can go to the GitHub pages for android-nn-driver, armnn and computelibrary (clframework) and download versions with the same release tag. +This will download the correct versions of boost, armnn and the clframework and the android-nn-driver should build correctly. Alternatively you can go to the GitHub pages for android-nn-driver, armnn and computelibrary (clframework) and download versions with the same release tag. For 19.08 these would be: @@ -33,6 +40,10 @@ https://github.com/ARM-software/android-nn-driver/tree/v19.08 https://github.com/ARM-software/armnn/tree/v19.08 https://github.com/ARM-software/computelibrary/tree/v19.08 +The correct version of boost (1_64_0) can be downloaded from: + +https://www.boost.org/ + Instance Normalization test failures ------------------------------------ |