You are correct. That was an oversight on my part. I've corrected it. Milestones: 1.x_My.rcz Major releases: 1.x and they should also get the name-x.y.z tag When Richard tells me :) -- Elizabeth

Jessica and Mark, Thank you for the responses. It appears that there is another thread on the same subject. Let me feedback what I am seeing and hearing: The quick start

I am not sure what the best way to clear up terminology is at the moment, and given it is he week before Christmas, a number of people I would like to discuss this with are on holiday, so we can defer

Right, none of the yocto- tools has anything to do with the meta-yocto layer, so if that's how it's taken, then, yeah, it's misleading. It wouldn't bother me to do a global search and replace of

Actually, BSP's should work standalone with oe-core, so it is of interest. I will now get pedantic. <rday mode on> The meta-yocto layer functions as a distro layer. So referring to things as yocto

I don't know the internals of bitbake on that level but as far as I understand, bitbake uses the name of the bbclass file as a prefix in the function names for the sake of abstraction. So, as in

2012/12/9 Bruce Ashfield <bruce.ashfield@...>: Dear Bruce, I'd like to have the same behaviour as before, so what you suggested would suit me. Could you please tell me where to add that

Technically it isn't any different, but it's based on the template engine code and templates that make up the 'Yocto BSP Tools', which for various reasons (they create Yocto-compliant BSP layers,

How is a "yocto layer" different from an OpenEmbedded layer? If you insist on "yocto layter", wouldn't "Yocto Project layer" be more accurate. One of our goals for next year should be to clean up our

Hello all, I'm using yocto project to create a linux for a IMX28. I currently insert these layers: poky/meta poky/meta-yocto meta-fsl-arm meta-openembedded/meta-oe I want to use JRE (Java Runtime)

On Tue, Dec 18, 2012 at 7:28 AM, Biao <huanmateme@...> wrote: At 2012-12-17 23:37:52,"Eren Türkay" <eren@...> wrote:>On Mon, Dec 17, 2012 at 05:06:26PM +0800, Biao wrote:>> Greetings, >> >> I am a

At 2012-12-17 23:37:52,"Eren Türkay" <eren@...> wrote:>On Mon, Dec 17, 2012 at 05:06:26PM +0800, Biao wrote:>> Greetings, >> >> I am a newbie tying to understand how bitbake works.>> There is one

I think the problem is that there isn't a system - there's a mix of tag naming. If you know the name of a release and the corresponding oe-core/Poky versions all the tags are present, but that's not

Hi Jessica, Zhang, Jessica wrote, On 15.12.2012 00:37: The first version of this RFC was meant to be a proof of concept, that's why I only included the ADT manual. One of the reasons why I integrated

In message <20121215132238.503DC201C62@...> I wrote: No comments anybody? Thanks in advance! Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk &

I believe a rebase is needed and please sent to oe-core mailing list. Thanks Sau! ___________________________

Hi, I'm glad to hear that the bitbake manual is getting an update, and I'm sure you guys know a lot of debugging tricks that I don't know. Can you please include a section on debugging bitbake build

The public git repository experimental/meta-tpm has been replaced with experimental/meta-trusted which will include libraries and tools that are not necessarily TCG/TPM destined as well as the work

The basic rule is that for a file: uri in a SRC_URI field, relative to the .bb it searches $PN-PV, $PN, then files/. Obviously there are complications with extending that search path, and .bbappends

I have not tested this back on Danny, but it seems to be past the point where it couldn't find anything. I have no idea how it worked in the past. I remember having to toy with it a lot. I'm still