[yocto] How Does Yocto Fill In UBOOT_MACHINE?

Leo Schwab lschwab at sensity.com
Thu Aug 15 13:21:48 PDT 2013


On Thu, Aug 15, 2013 at 12:41 PM, Saul Wold <sgw at linux.intel.com> wrote:
> What version of oe-core / bitbake are you working with?
>
Umm...  Is 'dylan' a meaningful answer?

> Sound likeyou are trying a clean build, you could just try "bitbake -e
> u-boot" without doing a full build and check those two items, the -e will
> also give you the do_compile() task.
>
Ooo, interesting.  'bitbake -e' all by itself gives me this:

----
# $UBOOT_MACHINE
#   set /home/ewhac/devel/iMX6/fsl-community-bsp/sources/meta-belis3/conf/machine/ourboard.conf:12
#     "mx6dl_sabresd_config"
UBOOT_MACHINE="mx6dl_sabresd_config"
----

But 'bitbake -e u-boot' gives me this:

----
# $UBOOT_MACHINE [4 operations]
#   set /home/ewhac/devel/iMX6/fsl-community-bsp/sources/meta-belis3/conf/machine/ourboard.conf:12
#     "mx6dl_sabresd_config"
#   finalize ast.py:331 [finalize]
#     "was: mx6dl_sabresd_config"
#   override[ourboard]:set
/home/ewhac/devel/iMX6/fsl-community-bsp/sources/meta-belis3/recipes-bsp/u-boot/u-boot-imx_2009.08.bbappend:5
#     "mx6_ourboard_config"
#   finalize override[ourboard]:
#     "mx6_ourboard_config"
# computed:
#   "mx6_ourboard_config"
UBOOT_MACHINE="mx6_ourboard_config"
----

And the generated do_compile() script reflects this.  Still not
entirely clear why the results differ.

Thank you for all the suggestions so far.

Schwab



More information about the yocto mailing list