Hi everyone,
I'm trying to add a target to AOSP which builds an additional single
output file for my board. Specifically, I want the build process to
generate a u-boot installation script (from a text source file), and
then place it in the out/ folder alongside the filesystem images for
my board.
I've been aping the make setup for 'installed-file-list.txt' in build/
core, because it looked similar. The current (non-working) section in
my board's makefile is:
# Installer u-boot script, generated to output directory
UBOOT_INSTALL_SCRIPT := $(PRODUCT_OUT)/scriptcmd
UBOOT_SRC_FILE := vendor/wm8505/installer/cmd
$(UBOOT_INSTALL_SCRIPT): $(UBOOT_SRC_FILE)
mkimage -A arm -O linux -T script -C none -a 1 -e 0 \
-n "Android WM8505 Installer" \
-d $(UBOOT_SRC_FILE) $(UBOOT_INSTALL_SCRIPT)
$(call dist-for-goals, droidcore, $(UBOOT_INSTALL_SCRIPT))
... The makefile is definitely evaluated when building but the $
(UBOOT_INSTALL_SCRIPT) target is never built. I've tried passing goals
like 'droid' or 'sdk' to dist-for-goals but that doesn't seem to
change anything.
I assume I'm missing something fundamental in the way AOSP puts
together its list of targets. Can anyone tell me what that is, or
where I might look? I feel like I'm going in circles, and debugging
GNU make is not something I want to do!
Thanks in advance.
- Angus
--
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
