Thanks Jessica, why I tried to use "-c populate-sdk" is because that I can find "core-image-sato-sdk" but no "core-image-basic-sdk" available, and my hardware is a samll jasperforest x86_64 target

Hi Eddy, The SDK is meant to be used on development host for cross development instead of target. Sounds like you need an sdk image which contains the development tools and needed development

From: Philipp Wagner <mail@...> Often the OpenGL libraries are dlopen'ed rather than linked against, which makes it necessary to add OpenGL libraries to RDEPENDS of the package. This

From: Philipp Wagner <mail@...> Depending on the used calling convention use the hardfp or the softfp binary graphics libraries. Signed-off-by: Philipp Wagner

Hi, I'm working on an application that needs the graphics libraries. Right now I'm still using the binary libraries (which are still default in meta-raspberrypi). Unfortunately, the current default

Folks, We would normally start the Milestone Build in the morning, so that it would be available by the afternoon and next day in Asia and Europe, at this point the release is ready, we are waiting

We're working on making the kernel lab available online. Until then, the materials would not be of much use as they were just specific enough to the lab machines we set up, that they would frustrate

Hi all, would be available slides and worksheet for the other YDD-2012 labs? - "Hands on kernel lab" by Darren & Tom - "YP eclipse plugin and HOB" by Jessica - "Yocto Project Layer for In-Vehicle

OpenEmbedded has a stand at FOSDEM. If you will be there stop by and say hi, or better yet, help man the stand for a while. http://www.openembedded.org/wiki/FOSDEM_2013 Philip

From: Timo Mueller <timo.mueller@...> As the eclipse generation is currently not part of the master the generation is always using the origin/timo branch to generate the eclipse help. This

From: Timo Mueller <timo.mueller@...> When building the plugin the matching documentation is automatically generated and added to the user.doc plugin prior to the plugin

From: Timo Mueller <timo.mueller@...> After successful generation the eclipse help files and the table of contents of each manual are copied to the user.doc plugin. Signed-off-by: Timo

From: Timo Mueller <timo.mueller@...> The separate yocto manuals are added to the table of contents to prepare their inclusion into the plugin. Signed-off-by: Timo Mueller

From: Timo Mueller <timo.mueller@...> This script will checkout the yocto-docs project containing the official yocto documentation. After successful checkout the eclipse help is generated

From: Timo Mueller <timo.mueller@...> Signed-off-by: Timo Mueller <timo.mueller@...> --- scripts/build.sh | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff

From: Timo Mueller <timo.mueller@...> Signed-off-by: Timo Mueller <timo.mueller@...> --- features/org.yocto.sdk.site/category.xml | 4 ++++ features/org.yocto.sdk.site/site.xml

From: Timo Mueller <timo.mueller@...> Signed-off-by: Timo Mueller <timo.mueller@...> --- features/org.yocto.doc.headless.build/.project | 11 +

From: Timo Mueller <timo.mueller@...> Signed-off-by: Timo Mueller <timo.mueller@...> --- features/org.yocto.doc/.project | 17 ++++

From: Timo Mueller <timo.mueller@...> As documentation is licensed under CCA-SA 2.0 UK and the plugin itself is licensed under EPL v1.0 an about file needs to be added to the plugin

From: Timo Mueller <timo.mueller@...> Adds yocto specific eclipse help to the plugin. The help is currently empty but will contain the official yocto documentation later. Signed-off-by: