"Android P" being built when I compile from AOSP Master?

[moh.maya]

Hello,

I’m a newbie trying to build ASOP (with Neonkey) for the 960 board. When I run

lunch hikey960-userdebug

as given in the instructions, the process output is as follows:

============================================
PLATFORM_VERSION_CODENAME=P
PLATFORM_VERSION=P
TARGET_PRODUCT=hikey960
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=cortex-a73
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv8-a
TARGET_2ND_CPU_VARIANT=cortex-a73
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.13.0-36-generic-x86_64-ubuntu-16.04.4-LTS
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=OC-MR1
OUT_DIR=out
============================================

Does this mean that the master build has been updated to the Android P preview release, as opposed to Android O?

Thank you!

[doitright]

Its more than “O” and less than “P”.

[danielt]

What he said!

Basically the master branch tends to get its letter updates for the next release almost as soon as the previous release is branched off. In other words adopting “P” warns people it contains code beyond the scope of “O”.

Historically AOSP contains community contributions for “P” but Google typically does some of its development in private and the final “P” codebase will be a merge of the public and private “P” trees.

[moh.maya]

got it; thank you! I managed to get android to boot, but there are issues with my app that I am not entirely sure are due to app issues or the build itself. I will try & build with Android O by changing the version in the build command and see what happens.

Again, thank you for replying!

[doitright]

That won’t work. Hikey960 is not fully supported except in master.