just to clarify any overlooked issues ... should one still change the NAME or DESCRIPTION comments in that new mymachine.conf file to reflect "mymachine" as the dev-manual suggests, or can one just le

... all of tom's stuff snipped ... ok, based on combining everything in the last several posts, my build for core-image-sato for the new "mymachine" bsp just finished successfully on my 64-bit ubuntu

currently the download URLs are a bit confusing. first, there's http://www.yoctoproject.org/download which takes you to the "download" page. then there's the ever so similar URL: http://www.yoctoproje

since i vaguely recall that i was the one who asked about this, i can submit a patch for this unless someone else already wants to. i can see that the places to change would be in some of the docs, as

Signed-off-by: Robert P. J. Day <rpjday@...> --- diff --git a/README b/README index 981786d..1eee6ca 100644 --- a/README +++ b/README @@ -18,7 +18,7 @@ e.g. for the hardware support. Poky i

stumbled over this so i did a more thorough search: $ grep -w PARALLEL_MAKE $(find . -name *.bb) ./meta/recipes-qt/qt-apps/qmmp_0.5.1.bb:PARALLEL_MAKE = "" ./meta/recipes-core/eggdbus/eggdbus_0.6.bb:P

ok, makes sense, thanks. rday

ok, i've been properly chastised. movin' on ... rday

current poky ref manual seems pretty adamant about need for LIC_FILES_CHKSUM: "Note that this variable is mandatory for all recipes, unless the LICENSE variable is set to "CLOSED". but there's at leas

oooookay, but it's really not hard to find more examples like that, such as meta-demoapps/recipes-graphics/libxklavier/libxklavier_3.9.bb: DESCRIPTION = "Utility library to make using XKB easier" SECT

Signed-off-by: Robert P. J. Day <rpjday@...> --- all of the atom pc info is already in that file, all that was missing was the entry for it in the early list. diff --git a/README.hardware b

oh, crap, you're right. sorry. rday

i'm sure it's in one of the docs i missed, but how does one cleanly shut down a QEMU session and get back to the original terminal session? i've tried shutdown and poweroff but neither of those gives

qemuppc, core-image-minimal. interestingly, "poweroff" doesn't completely close the QEMU session, but "reboot" does. it might be worth adding that to the quick start guide. rday

i asked this on the beagle list, and koen pointed out that it was probably more appropriate elsewhere (probably here). what's the proper algorithm for building the leading-edge images for a beagle xM

ok, that's perfectly reasonable -- meta-yocto provides a generic, well-tested product, while the meta-ti layer provides more leading-edge content, correct? which is a perfectly respectable answer. but

i understand that reasonably well, and i'll make one more observation, then i'll shut up. i cloned the meta-ti layer into my yocto clone, and here's the majority of the meta-ti README: ===== start Thi

as it is, if someone new to yocto checks out the git tree and sees the documentation/ directory, they'll immediately hop in there, see the possible manuals and perhaps run "make" to try to build them,

just starting to go thru the thread regarding the QS guide and i have to agree that there's probably too much lead-in when the people reading the QS guide are probably competent enough to just want th

since it's easier to just write something than suggest numerous fixes, i took less than an hour and wrote this: http://www.crashcourse.ca/wiki/index.php/Yocto_Project_Quick_Start it's the sort of thin