maybe i'm misreading something, but the yocto QS guide provides the sample command: $ bitbake -k poky-image-sato however, nothing provides that target. i can see the git log entry: commit

I think we have all the pieces there but someone would have to connect them up... Cheers, Richard

Correct, or at least not that I've used out of the box, and this is what Koen was commenting on. Cheers, Bruce

Ugh, sorry. Bug #1244 to track http://bugzilla.pokylinux.org/show_bug.cgi?id=1244 Yeah, I sucked at designing use cases. This is already filed as bug #1239

Try this: bitbake -u hob -> Python traceback change PARALLEL_MAKE from 'j8' to 'j 8' bitbake -u hob click save Open up recipe in editor -> 'require None.bb' So it looks like creating an image

Fix some obvious typoes in a couple "opkg-cl" commands in the ADT manual, packages chapter. Signed-off-by: Robert P. J. Day <rpjday@...> --- i'm *hoping* i'm reading this correctly.

If you have questions please ask them. The saved file should be a recipe for building a custom image. The purpose of the tool is to help you put together a custom image and build

Fix missing prompt, missing "git" and break overly long command in two since it disappears off the page in the PDF output. Signed-off-by: Robert P. J. Day <rpjday@...> --- these fixes

Ah, so there isnt support for getting a ramdisk wrapped via mkimage. - k

Are they thread of email discussion or anything. I tried playing with it, but a little confused on exactly what its trying to accomplish and what the 'cfg' that is saved off ends up being. - k

and to expand a bit, the machine conf would have: KERNEL_IMAGETYPE = "uImage" So the kernel class will build and produce a uImage for deployment. Cheers, Bruce

None, it's built by the kernel class, not the rootfs class.

What's the IMAGE_FSTYPE for a normal uImage ? - k

From: Tom Zanussi <tom.zanussi@...> AIGLX wasn't finding a couple libraries, causing errors such as Yocto bug #1235 - 'Running glxinfo and glxgears commands failed.'. This provides symlinks

From: Tom Zanussi <tom.zanussi@...> This is a fix for Yocto bug #1235. The following changes since commit 92fc07a5f1b98779806cdcc2341487ff5ea5a238: Dexuan Cui (1): emenlow: fix some

Robert, I know that and will work towards that end as well. There are a lot of holdover things in our docs. Thanks, Scott

and while you're at it, i was once lectured sternly that the proper spelling is "Git" when talking about the tool and "git" when referring to the actual command. never "GIT". at least that what i

Merged to master, thanks. Richard

Agreed that BitBake is the correct spelling. I will be sure to make a sweep through our Yocto manuals and make sure that when we are referring to the tool and not indicating the command they say

Yah, that's what I wondered as well. I've done this locally, but nothing out of the box .. so I had nagging doubts! Cheers, Bruce