Generally it's a good idea to use the tools paired with the branch. But in
ccache's case, the binaries are the same for M, N, O, and newer. With the
build system you're always going to use the ccache binary paired with the
tree anyways -- you just set USE_CCACHE=1. The only time you'd use the
Android 8.1.0 Oreo MR1 source code is now available. The following builds,
tags, and devices are supported:
- OPM1.171019.026, android-8.1.0_r19, Pixel C
- OPM2.171019.029, android-8.1.0_r20, Pixel 2 XL (taimen), Pixel 2
(walleye), ixel XL (marlin), Pixel (sailfish), Nexus 5X (bullhead)
-
B00095315:workspace tonglele$ make clobber
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=8.0.0
TARGET_PRODUCT=aosp_arm
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a
Hi Dan, sorry for the delayed response and thanks for the tip! I opted to
rebuild my environment on a more capable physical Linux machine and the
build passed ok :)
One thing though is that I’m having trouble running the built image on a
different (mac) machine.
I copied the image files from
I built the latest release: AOSP 8.1.0_r18 and attempted to run it in the
emulator on the same machine.
The emulator runs and I get the home screen but it also displays some
errors..
jumbo@ubuntu-14:~$ cd android
jumbo@ubuntu-14:~/android$ source build/envsetup.sh
including
Hi Ye Roger,
Did you happen to found any solution on this problem, or the reason why
this problem occurred?
On Saturday, June 4, 2016 at 12:27:18 AM UTC+9, Ye Roger wrote:
>
> I know that there may not have people interested in the old build.
> However, I do need to build an emulator x86
I figured out that i my sdk version was incorrect.
In my case, i switched to oracle-6-java for java, javac, javaws but my
javadoc was still using java-8. (javadoc -J-version was 1.8.xx)
On Saturday, June 4, 2016 at 12:27:18 AM UTC+9, Ye Roger wrote:
>
> I know that there may not have people
