From: Denys Dmytriyenko <denys@ti.com>
To: Nicolas Dechesne <ndec13@gmail.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: building yocto images with meta-ti
Date: Wed, 19 Sep 2012 09:57:00 -0400 [thread overview]
Message-ID: <20120919135659.GA589@edge> (raw)
In-Reply-To: <CAOT3mi+f4Wsaba4S3uiw1p27R585EBY4OSA8K=pPCpbATwRmcA@mail.gmail.com>
On Wed, Sep 19, 2012 at 08:16:05AM +0200, Nicolas Dechesne wrote:
> hi there,
Hi Nicolas,
> i was able to build a 'vanilla' yocto image using the yocto git repo.
> then i wanted to add meta-ti layer. so i have done the following:
First, a little rant... :)
It's unfortunate, but this still causes lots of confusion. Some purists among
us will say that is not Yocto, but Poky. Case in point - which "yocto" git
repository you cloned from http://git.yoctoproject.org/ ?
Same applies to a 'vanilla' yocto image, which does not exist. It would rather
be useful to specify which exact image for which MACHINE you are trying to
build. A little bit more detail is always helpful...
And now to the resolution part. I see you already used BBMASK as prescribed in
the README, since you get past the unset LICENSE error... The below error
happens when you build for a MACHINE that is overshadowed by another BSP
layer that does not define MACHINE_KERNEL_PR. This MACHINE_KERNEL_PR variable
is set in MACHINE definitions of meta-ti BSP layer and then used in other
recipes within meta-ti and different layers.
In other words, you are trying to build for "beagleboard" machine, which gets
also defined by meta-yocto-bsp layer, besides meta-ti. The solution is simple -
you need to move meta-ti above meta-yocto-bsp in your bblayers.conf or just
remove meta-yocto-bsp from the list, if you are not planning on building any
of the reference platforms. That way you'll get the machine definition from
meta-ti layer and not from meta-yocto-bsp.
After that, core-image-minimal and some other images should build fine. Good
luck!
--
Denys
> - clone git://git.yoctoproject.org/meta-ti
> - modify BBLAYERS in conf/bblayers.conf to add meta-ti
>
> i can verify that meta-ti layer is configured properly as
> bitbake-layers show-layers shows it just fine (with priority 10).
>
> However parsing recipes failed with:
>
> Loaded 23 entries from dependency cache.
> ERROR: ExpansionError during parsing
> /work/yocto/meta-ti/recipes-ti/local-power-manager/ti-local-power-manager_1.24.02.09.bb:
> Failure expanding variable FILESPATH, expression was
> ${@base_set_filespath([
> "/work/yocto/meta-ti/recipes-ti/local-power-manager/ti-local-power-manager-1_1_24_02_09-${MACHINE_KERNEL_PR}e",
> "/work/yocto/meta-ti/recipes-ti/local-power-manager/ti-local-power-manager-1_24_02_09",
> "/work/yocto/meta-ti/recipes-ti/local-power-manager/ti-local-power-manager",
> "/work/yocto/meta-ti/recipes-ti/local-power-manager/ti-local-power-manager-1_24_02_09",
> "/work/yocto/meta-ti/recipes-ti/local-power-manager/ti-local-power-manager",
> "/work/yocto/meta-ti/recipes-ti/local-power-manager/files",
> "/work/yocto/meta-ti/recipes-ti/local-power-manager" ], d)} which
> triggered exception SyntaxError: EOL while scanning string literal
> (FILESPATH, line 1)
> ERROR: Command execution failed: Exited with 1
>
> is there a particular commit in yocto that meta-ti requires?
>
> how do you guys generate vanilla yocto images with meta-ti?
next prev parent reply other threads:[~2012-09-19 13:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 6:16 building yocto images with meta-ti Nicolas Dechesne
2012-09-19 6:28 ` Koen Kooi
2012-09-19 6:56 ` Andrea Galbusera
2012-09-19 13:57 ` Denys Dmytriyenko [this message]
2012-09-19 16:04 ` Nicolas Dechesne
2012-09-19 16:26 ` Trevor Woerner
2012-09-19 16:33 ` Denys Dmytriyenko
2012-09-19 16:26 ` Denys Dmytriyenko
2012-09-20 7:40 ` Nicolas Dechesne
2012-09-20 8:42 ` Jack Mitchell
2012-09-20 12:22 ` Dmytriyenko, Denys
2012-09-21 8:44 ` Nicolas Dechesne
2012-09-21 8:49 ` Koen Kooi
2012-09-21 9:11 ` Nicolas Dechesne
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120919135659.GA589@edge \
--to=denys@ti.com \
--cc=meta-ti@yoctoproject.org \
--cc=ndec13@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.