Android 10 AOSP build integration fails with ckati errors
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
Following the tutorial to compile MicroG with a local manifest and Android 10, the AOSP build system fails:
packages/apps/GmsCore/Android.mk:36: error: writing to readonly directory: "packages/apps/GmsCore/play-services-core/build/outputs/apk/release/play-services-core-release-unsigned.apk"
19:53:21 ckati failed with: exit status 1
This same error exists for FakeStore and GmsProxy. I attempted a ghetto work around of adding BUILD_BROKEN_PHONY_TARGETS := true to BoardConfig.mk, which just fails with another deprecation error:
packages/apps/GmsCore/Android.mk:29: error: ANDROID_BUILD_TOP is obsolete. Use '.' instead. See https://android.googlesource.com/platform/build/+/master/Changes.md#ANDROID_BUILD_TOP.
13:35:31 ckati failed with: exit status 1
Are there updated makefiles to use when building with AOSP sources, or do I have this misconfigured?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing packages/apps/GmsCore/Android.mk, especially lines 29 and 36, with the Android 10 AOSP build guidance in Changes.md, then reproduce the build for GmsCore, FakeStore, and GmsProxy. Done means the local-manifest AOSP build completes without readonly-directory or ANDROID_BUILD_TOP/ckati errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- build-system, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100