Build Neonkey binary from AOSP master


#1

Hi, just starting developing with the Hikey960 and Neonkey boards.

For starters, I’m trying to build the neonkey firmware within an AOSP as per the instructions here: https://source.android.com/setup/build/devices#neonkey

However, the build fails with:
make[1]: *** No rule to make target ‘os/algos/calibration/magnetometer/mag_cal.c’, needed by ‘out/nanohub/neonkey/os.unchecked.elf’. Stop.

Of course I can fix this particular issue but then there’s the next one and next one so before going down the rabbit hole I’d like to ask am I taking the right path here or would I be better off getting the “neonkey AOSP firmware” from somewhere else? Should this still work and I should report this issue to AOSP?

The AOSP master has been synced yesterday “2018-08-10” and the git log in “aosp/device/google/contexthub/firmware” says:

"commit b3211319af620de5a7ed701e383deb3dc8d866f8 (HEAD, tag: android-o-mr1-iot-release-1.0.3, m/master, aosp/oreo-mr1-iot-release, aosp/master)
Merge: 51c32d5b 52da962a
Author: Xin Li delphij@google.com
Date: Mon Aug 6 16:50:08 2018 -0700

Merge Android Pie into master

Bug: 112104996
Change-Id: I5786617e5db720dc171326bfbf52920d6b88abf3"

#2

+1
I’ve added the bug report since I 'm seeing the same issue after you reported it.
You can follow it here: https://bugs.96boards.org/show_bug.cgi?id=764

Thaks!


#3

Thank you for your response ric96.

In the meantime, I was able to build the project by going back in the history to the tag “android-p-preview-5” (just in case someone would be interested while waiting for the fix).


#4

Can you try again with the master branch now? A fix was pushed last night.


#5

Yes, it works now. Thank you.