This is just a generic warning on the subject of native patch. We recently had a discussion on the LTSI-dev mailing list about patch. It seems that some patches produced by git now require a later ver

Hi everyone, I'm doing research on whole-system optimization, and I'd like to ask opinions on the next stage of my work. == background == After a fair amount of blood, sweat and tears, I have (finally

Aha. Thanks very much. Is this the preferred way to get a toolchain out of yocto? That's exactly what I'm working on at the moment (well, after fixing up some toolchain build issues I've encountered a

I was reading in the adt manual about using the cross-toochain tarball, and I came across this sentence: "If you need GMAE, you should use the bitbake meta-toolchain-gmae command. The resulting instal

Just to answer my own question... In bitbake in poky-danny-8.0, (poky-danny-8.0/bitbake/lib/bb/cooker.py) bbmask_compiled.search() is used, which means that the leading ".*" is unnecessary. A python r

That's how I do it. I'm not sure if there's some other preferred method or not. This should catch that name in all layers. -- Tim ============================= Tim Bird Architecture Group Chair, CE Wo

Indeed. These would be good clarifications. The manual says that this is a single python regular expression. Hence, when masking multiple directories or recipes, you use a vertical bar to separate the

Hmmm. With bitbake from poky-1.2-denzil I get: "Nothing to do. Use 'bitbake world' to build everything, or run 'bitbake --help' for usage information." I think that "bitbake <nothing>" is not really a

Yeah - this looks great. I put a link to your page on my bitbake cheat sheet page at: http://elinux.org/Bitbake_Cheat_Sheet ============================= Tim Bird Architecture Group Chair, CE Workgrou

It looks very useful. I put a link to it from my elinux page on Yocto. -- Tim ============================= Tim Bird Architecture Group Chair, CE Workgroup of the Linux Foundation Senior Staff Enginee

Never mind. I figured it out. It's 'ctrl-a <key>', with 'ctrl-a x' to terminate the qemu session. ============================= Tim Bird Architecture Group Chair, CE Workgroup of the Linux Foundation

This is working now. Thanks. BTW - how do I stop the kernel/emulator? There's no 'shutdown', and 'halt' and 'reboot' don't do anything. Is there a key sequence to get back to the qemu monitor?? There'

Ahh. That's helpful. Thanks. I'd be happy to write some stuff up. It wouldn't be exhaustive, but I could document what I've found out about (the LIBC_FEATURE stuff, and some of the dependencies I've f

I'll see if I can find something. Building poky-tiny with core-image-minimal worked fine. I didn't understand that this built multiple images (including a cpio.gz), and thought that the default method

Hi all, I'm using DISTRO=poky-tiny and trying to build: $ bitbake core-image-minimal-initramfs I get the following error trying to compile diffutils: ... i586-poky-linux-gcc -m32 -march=i586 --sysroot

I am in the process of creating my own distro, and trying to figure out all the different build variables. This is a pretty daunting task for a yocto project/Poky newbie. Is there some place where the

I am in the process of creating my own distro, and trying to figure out all the different build variables. This is a pretty daunting task for a yocto project/Poky newbie. Is there some place where the

(I answered Scott privately by mistake - here's some feedback on-list) I'm in favor of mentioning the history somewhere, because the names do have a 'P' in them, and this is confusing otherwise. Overa

From Jeff's description, it sounded like the package (especially 'package version') comes from the stuff that is the recipe's *input*, and not the recipe's output -- if you've selected to build packag

I'm not an expert, but here's some information that I believe is correct. (If someone else knows better, please correct this...) bitbake reads the entire set of recipe files that are specified by the