Re: yocto-bsp create


Tom Zanussi <tom.zanussi@...>
 

On Fri, 2012-08-17 at 20:56 +0100, Chris Tapp wrote:
On 17 Aug 2012, at 20:47, Bruce Ashfield wrote:

On 12-08-17 03:40 PM, Chris Tapp wrote:

On 17 Aug 2012, at 20:33, Bruce Ashfield wrote:

On 12-08-17 03:32 PM, Chris Tapp wrote:
On 17 Aug 2012, at 15:59, Bruce Ashfield wrote:

On 12-08-17 06:47 AM, Chris Tapp wrote:

On 17 Aug 2012, at 00:48, Bruce Ashfield wrote:

ech. That means that the tree was somehow dirty and branches couldn't
be switched/checked out.

If you have a copy of your BSP layer, I can try a build here and shed
some light on what exactly went wrong.

Thanks Bruce. Meta layer attached.
Fixed here. This was completely generated from the tools ? If so, the
branching information was wrong.

KBRANCH_LX800 = "standard/default/LX800"
YOCTO_KERNEL_EXTERNAL_BRANCH_LX800 = "standard/default/LX800"

The "base" is always inferred and only exists because of the
way that git manages refs on disk. So the branch that you
want to build is what I have above, and the tools will
automatically make that branch point off the default/base
branch.

Let me know if that did come from the tools and I'll follow
up to the list.
I'm 99.99% sure it did, but it runs ok after making the changes you give above, deleting tmp/ and rebuilding.

I've not g0t any real changes in yet, so I'll go try again and see what I get. It's just possible I didn't do a complete rebuild (i.e. nuke tmp/) which may have caused a problem last time round.
ok. cool. no rush. I was just going to do a final update on the mailing
list to not leave it hanging, and if there's a bug in the scripts, we
can let Tom know .. so he can fix it!

I've just recreated the BSP. I selected option 4 for the kernel branch (standard/default/base), which gives:

KBRANCH_LX800 = "standard/default/base/LX800"
YOCTO_KERNEL_EXTERNAL_BRANCH_LX800 = "standard/default/base/LX800"
ok. Worth firing off a bug report to Tom Zaunussi. .. that
won't work .. ever.
Just bringing this back on-list.

I'll get something added to the tracker.
Just back from vacation and getting to this...

Yeah, this is a known bug and was fixed by the yocto-bsp patchsets I
sent out just before I left. See the last entry in the bug below for
links to the branches that fixed it and a few other issues:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=2693

I see that the denzil branch has been updated with the changes, but have
yet to hit master.

Tom

Chris Tapp

opensource@...
www.keylevel.com



_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto

Join {yocto@lists.yoctoproject.org to automatically receive all group messages.