When building our custom SDK add-on, the system image that is generated alongside does not include our custom kernel image by default (actually, any kernel image…not even the default QEMU image) so any AVDs generated from it do not work unless we manually copy a kernel image as part of the add-on, i.e.:
PRODUCT_SDK_ADDON_COPY_FILES += $(LOCAL_KERNEL):images/armeabi-v7a/kernel-qemu …the problem with doing this, as you might imagine, is we are hard-coding an ABI into the path. If we build the target for another architecture the file copy won't work correctly. What is the proper way to include a custom kernel image in an SDK add-on? Furthermore, if we didn't have a custom image, how would we have the default images copied in? I don't see anything in the build task related to the kernel (https://android.googlesource.com/platform/build/+/android-5.0.1_r1/core/tasks/sdk-addon.mk). We have tried arch-specific variables in our existing copy path, i.e.: PRODUCT_SDK_ADDON_COPY_FILES += $(LOCAL_KERNEL):images/$(TARGET_CPU_ABI)/kernel-qemu …which evaluates to nothing at that stage of the build. Something like this is not ideal, but if we are required to use a manual copy declaration it would allows us to avoid duplicating for makefile for each arch. -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to adt-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
