docs(zero3/android): fix Android build manifest branch from rk11 to rk12 - #1995
Open
tangzz-radxa wants to merge 1 commit into
Open
docs(zero3/android): fix Android build manifest branch from rk11 to rk12#1995tangzz-radxa wants to merge 1 commit into
tangzz-radxa wants to merge 1 commit into
Conversation
The lowlevel-development page instructed 'repo init -b Android11_Radxa_rk11', but the zero3 device config (rk356x_radxa_zero3) only exists in the Android11_Radxa_rk12 manifest (tag radxa-android11-rkr12.2). Users following the old instructions got 'Can not locate config makefile for product rk356x_radxa_zero3'. Fixes radxa-docs#1878.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #1878 — Zero 3 Android build fails with
Can not locate config makefile for product "rk356x_radxa_zero3".Root cause
The lowlevel-development page told users to initialize the Android 11 manifest with:
But the
rk356x_radxa_zero3device configuration only exists in the Android11_Radxa_rk12 manifest branch (device/rockchip/rk3566 pinned to tagradxa-android11-rkr12.2). With the rk11 manifest, the synced source tree has no zero3 device folder, solunch rk356x_radxa_zero3-userdebugcannot locate the product config.This is also consistent with the download page, which already references the
rkr12release image (radxa-zero3-we-android11-rkr12-20240111).Change
docs/zero/zero3/other-os/android/lowlevel-development.md(zh)i18n/en/docusaurus-plugin-content-docs/current/zero/zero3/other-os/android/lowlevel-development.md(en)Both updated:
-b Android11_Radxa_rk11→-b Android11_Radxa_rk12.Verified: the rk12 manifest (
Android11_Radxa_rk12_customization.xml) pinsdevice/rockchip/rk356xto revisiond4bfc34f(tagradxa-android11-rkr12.2), whose tree containsrk356x_radxa_zero3/withrk356x_radxa_zero3-userdebugproduct entries.docs-only, bilingual in sync.