On 03/31/2011 11:15 PM, Li, Simon wrote:
Hi, Saul,
Thanks for your reply. However, I got error messages as below:
It seems not support "poky-image-sato-sdk"
Simon for 0.9 version then it would be poky-image-sdk, we changed the
image name in 1.0. Sorry for the confusion.
Sau!
===
On 04/01/2011 12:37 AM, Li, Simon wrote:
Hi, Gary,
Yes, it works. However, after build finished, I still cann't find any libQt*
files.
Where did you look (what packages did you install)?
Just add this line to your config:
IMAGE_FEATURES += "qt4-pkgs"
This should then build an image which ha
Hello Jessica,
On Mon, Mar 14, 2011 at 10:56 PM, Leon Woestenberg
wrote:
> On Sun, Mar 13, 2011 at 12:55 AM, Zhang, Jessica
> wrote:
>> Leon Woestenberg wrote:
>>> built, I wanted to test the Eclipse plug-in. After selecting Poky Tree
>>> mode in the Yocto Tool configuration, I could not make it
Leon Woestenberg wrote:
> Hello Jessica,
>
> On Mon, Mar 14, 2011 at 10:56 PM, Leon Woestenberg
> wrote:
>> On Sun, Mar 13, 2011 at 12:55 AM, Zhang, Jessica
>> wrote:
>>> Leon Woestenberg wrote:
built, I wanted to test the Eclipse plug-in. After selecting Poky
Tree mode in the Yocto To
The file seems to be copied from here by bitbake:
http://gcc.get-software.com/releases/gcc-4.5.0/gcc-4.5.0.tar.bz2
I manually downloaded it too it still shows up to be corrupted.
Not sure what does one do in such cases..
Thanks
Rahul
From: Tian, Kevin
Sent: Thursday, March 31, 2011 9:45 PM
To:
could you double confirm the link below is used in your side?
Ideally the gnu mirror should be used, e.g.
ftp://ftp.gnu.org/gnu/gcc/gcc-4.5.1/gcc-4.5.1.tar.bz2 in my log though it's
4.5.1
If the upstream tar ball itself is broken, there's nothing to do with bitbake
itself. You have to find an
The crownbay has been updated for 2.6.37, the BSP branch
already contans the changes, and this is the update of meta
to the new config values:
crownbay: update eg20t config
crownbay: set cpu type to MATOM
Signed-off-by: Bruce Ashfield
---
.../conf/distro/include/poky-default-revisions.inc |
Richard,
patch 1 in this series is a re-send of a previous change, since
it was still on the queue and it was worth keeping it in history
in order with the second change.
The second patch addresses [YOCTO #945], and the patch itself
has the following:
[
As part of the update to 2.6.37 existin
Fixes [YOCTO #945]
As part of the update to 2.6.37 existing configuration and
patches from the -stable kernel were left in place as a reminder
of features and configuration carry forward. A lot of these
reminders are no longer necessary and the kernel meta data
needs to be cleaned up to prepare fo
