[OE-core] "bitbake -c fetchall" doesn't appear to process EXTRA_IMAGEDEPENDS values
Robert P. J. Day
rpjday at crashcourse.ca
Wed Nov 21 10:41:12 UTC 2012
short followup to yesterday, it seems that running
$ bitbake -c fetchall ... whatever ...
won't fetch anything defined solely with EXTRA_IMAGEDEPENDS, although
the fetching *will* be done during the build.
in my case, using oe-core and meta-ti layers to build for
pandaboard, and here's the versions of u-boot allegedly part of the
process:
$ bitbake -s | grep u-boot
nativesdk-u-boot-mkimage :2011.06-r0
u-boot :2011.12-r8 <- there
u-boot-fw-utils :2011.06-r1
u-boot-mkimage :2011.06-r0
u-boot-mkimage-native :2011.06-r0
$
but the fetchall fetches only the 2011.06 version. a simple kludge
was to simply force the fetch by adding:
CORE_IMAGE_EXTRA_INSTALL = "u-boot"
to my local.conf before starting the fetch.
just FYI, the meta-ti layer uses this extensively:
$ grep -r EXTRA_IMAGEDEPENDS *
conf/machine/beagleboard.conf:EXTRA_IMAGEDEPENDS = "u-boot"
conf/machine/keystone-evm.conf:#EXTRA_IMAGEDEPENDS = "u-boot"
conf/machine/beaglebone.conf:EXTRA_IMAGEDEPENDS = "u-boot"
conf/machine/include/keystone.inc:EXTRA_IMAGEDEPENDS += "u-boot"
conf/machine/include/ti814x.inc:EXTRA_IMAGEDEPENDS += "u-boot"
conf/machine/include/davinci.inc:EXTRA_IMAGEDEPENDS += "u-boot"
conf/machine/include/omap4.inc:EXTRA_IMAGEDEPENDS += "u-boot"
conf/machine/include/omap3.inc:EXTRA_IMAGEDEPENDS += "u-boot x-load"
conf/machine/include/ti33x.inc:EXTRA_IMAGEDEPENDS += "u-boot"
conf/machine/include/ti816x.inc:EXTRA_IMAGEDEPENDS += "u-boot"
$
so is this an actual bug? or am i doing something silly?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
More information about the Openembedded-core
mailing list