| Issue 3384: | Build issue: PRODUCT_PACKAGES_DEBUG doesn't resolve the :32 :64 module names | |
| 1 person starred this issue and may be notified of changes. | Back to list |
***************************************************************** ***** ***** ***** !!!! THIS BUG TRACKER IS FOR GERRIT CODE REVIEW !!!! ***** ***** ***** ***** DO NOT SUBMIT BUGS FOR CHROME, ANDROID, CYANOGENMOD, ***** ***** INTERNAL ISSUES WITH YOUR COMPANY'S GERRIT SETUP, ETC.***** ***** ***** ***** THOSE ISSUES BELONG IN DIFFERENT ISSUE TRACKERS ***** ***** ***** ***************************************************************** Affected Version: What steps will reproduce the problem? 1. Create build module based on BUILD_PREBUILT template with using LOCAL_MULTILIB := 32, for example, with name SOME_MODULE (it should be some prebuilt apk with 32-bit libs) 2. Add this module to PRODUCT_PACKAGES_DEBUG (PRODUCT_PACKAGES_DEBUG += SOME_MODULE) 3. Create userdebug build What is the expected output? What do you see instead? Expected: Apk is included into the build Actual: Apk is not included Please provide any additional information below. If you change it to PRODUCT_PACKAGES_DEBUG += SOME_MODULE_32 or use PRODUCT_PACKAGES instead - it works. AOSP build system adds _32 or _64 prefixes to internal module names if LOCAL_MULTILIB is used. The logic processing PRODUCT_PACKAGES recognizes that fact and we do not need to add that suffix explicitly, but it is not accounted for PRODUCT_PACKAGES_DEBUG (and for _ENG too). You can refer to the logic in build/core/main.mk (search for "# Resolve the :32 :64 module name").
May 20, 2015
Project Member
#1
edwin.ke...@gmail.com
Status:
Invalid
|
|
| ► Sign in to add a comment |