Hi Darren,
On 14/06/12 22:09, Darren Hart wrote:
> This solution improves the kick-the-tires
> experience with poky-tiny, without pulling in all of init,
I think you really should quantify what 'all of init' means, without
this you are addressing a problem that is merely perceived. Just a quick
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/14/2012 5:17 PM, Tyler Jones wrote:
> I am compiling a distro for my hardware using DEBs for my package
> management. In meta/classes/package_deb.bbclass I need DPKG_ARCH =
> "armel" instead of TARGET_ARCH (which is "arm"). When I run dpkg on
> m
Hi,
On 14/06/12 22:42, Chris Tapp wrote:
> On 14 Jun 2012, at 21:44, Chris Tapp wrote:
>
>> The log for do_rootfs is showing: < snip > error: Failed
>> dependencies: libGL.so.1 is needed by libglut3-7.11-r13.2.armv6
>> libGL.so.1 is needed by column-wallboard-1.0-r1.armv6 libGL.so.1 is
>> needed
From: Tom Zanussi
emenlow needs to use the old 1.10.2 cairo library instead of the
upgraded version.
Fixes [YOCTO #2507]
Signed-off-by: Tom Zanussi
---
meta-emenlow/conf/machine/emenlow.conf |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/meta-emenlow/conf/machine/eme
From: Tom Zanussi
The emenlow graphics stack doesn't work with the cairo_1.12.2 library
upgrade; this adds the old 1.10.2 recipe from poky locally to the
emenlow layer in order to get it working again.
Fixes [YOCTO #2507]
Signed-off-by: Tom Zanussi
---
.../recipes-graphics/cairo/cairo_1.10.2.
From: Tom Zanussi
The recent upgrade of cairo to 1.12.2 broke meta-emenlow; keeping
the old 1.10.2 recipe around in the meta-emenlow layer gets it
working again.
The following changes since commit bd00e28dd54b06a1f01f186be168d3af872f96d4:
Richard Purdie (1):
meta-emenlow: Update qt4 bb
On Thu, Jun 14, 2012 at 7:29 PM, Kha wrote:
>
> I do 4 steps above and build successfully a Qt demo program on PC, but in
> qt4-demo-image, there are a lot of errors
>
> Can anyone solve this problem
>
> http://imageshack.us/photo/my-images/16/20120613234840.jpg/
>
> --
what steps did you use whe
1. cd to a /usr/bin/qtopia/demos/mainwindow (for example)
2. (qmake -project)
3. qmake -o Makefile mainwindow.pro
3'. (uic ui files)
4. make
I do 4 steps above and build successfully a Qt demo program on PC, but in
qt4-demo-image, there are a lot of errors
Can anyone solve this problem
http://i
Hi Belen,
I only know there have two variables we get from the bitbake to charge which
image is runnable, now.
"RUNNABLE_IMAGE_TYPES" = ext3, ext2, "RUNNABLE_MACHINE_PATTERNS" = qemu.
Thanks!
--
Liming
-Original Message-
From: Barros Pena, Belen
Sent: Thursday, June 14, 2012 11:09 PM
To
I am compiling a distro for my hardware using DEBs for my package
management. In meta/classes/package_deb.bbclass I need DPKG_ARCH = "armel"
instead of TARGET_ARCH (which is "arm"). When I run dpkg on my device armel
is the architecture, not arm, but yocto wants my TARGET_ARCH to be set to
"arm". I
On 14 Jun 2012, at 21:44, Chris Tapp wrote:
> The log for do_rootfs is showing:
> < snip >
> error: Failed dependencies:
> libGL.so.1 is needed by libglut3-7.11-r13.2.armv6
> libGL.so.1 is needed by column-wallboard-1.0-r1.armv6
> libGL.so.1 is needed by libglu1-7.11-r13.2.armv6
On 06/14/2012 08:09 AM, Barros Pena, Belen wrote:
> Hi all,
>
> The current Hob allows you to build images for a qemu machine selecting
> 'live' as your image type. To me (with my pitiful knowledge) this doesn't
> make much sense: would I want to deploy an image built for a
> virtualisation envi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/13/2012 11:58 PM, Khem Raj wrote:
> On 6/13/2012 10:21 PM, Darren Hart wrote:
>> At some point poky-tiny may need to come into oe-core, until
>> then...
>
> why do you think so. micro is also a distro with similar goals
> lives outside of OE-
On 06/14/2012 12:11 AM, Tomas Frydrych wrote:
> Hi Darren,
>
> On 14/06/12 01:33, Darren Hart wrote:
>> o Do not include the standard Busybox init
> ...
>> o Do not provide inittab functionality
>
> I am not entirely clear what you are hoping to gain by creating a home
> grown init solution?
C
The log for do_rootfs is showing:
ERROR: Function failed: do_rootfs (see
/media/SSD-RAID/build-denzil-pi/tmp/work/raspberrypi-poky-linux-gnueabi/sjs-x11-image-1.0-r0/temp/log.do_rootfs.8633
for further information)
Generating solve db for
/media/SSD-RAID/build-denzil-pi/tmp/deploy/rpm/raspberry
From: Tom Zanussi
Silence the warning:
WARNING: BBPATH references the current directory
as mentioned in [YOCTO #1465].
Signed-off-by: Tom Zanussi
---
meta-cedartrail/conf/layer.conf |4 ++--
meta-chiefriver/conf/layer.conf |4 ++--
meta-crownbay/conf/layer.conf |4 ++--
m
From: Tom Zanussi
Silence the warning:
WARNING: BBPATH references the current directory
as mentioned in [YOCTO #1465].
Signed-off-by: Tom Zanussi
---
conf/layer.conf |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/conf/layer.conf b/conf/layer.conf
index a5db163..b
From: Tom Zanussi
This patchset gets rid of the new layer warning for meta-intel
and all contained BSP layers.
The following changes since commit bd00e28dd54b06a1f01f186be168d3af872f96d4:
Richard Purdie (1):
meta-emenlow: Update qt4 bbappend to 4.8.1
are available in the git repositor
On 06/14/2012 11:05 AM, Robert P. J. Day wrote:
embarrassingly, i only just noticed that if i want my
yocto-generated qemu images to take advantage of kvm, i should add the
arg "kvm" to my "runqemu" invocation, is that correct?
Correct.
if that's the case, might it be worth adding that
On 06/14/2012 11:39 AM, Robert P. J. Day wrote:
just a few observations:
1) usage suggests this possible option:
MACHINE=xyz
not sure what that's supposed to accomplish, that will be rejected
by the arg parsing loop, will it not? or how is one supposed to
interpret that?
This is a
Bjorn, these are some interesting ideas.
Some feedback below.
This is from the perspective of asomeone who develops for embedded systems
boards
2012/6/14 Björn Stenberg
> Hi.
>
> Many source packages include their own package test suites. We are looking
> at running these tests on target in a st
just a few observations:
1) usage suggests this possible option:
MACHINE=xyz
not sure what that's supposed to accomplish, that will be rejected
by the arg parsing loop, will it not? or how is one supposed to
interpret that?
2) the process_filename() function appears to accept a filesyst
embarrassingly, i only just noticed that if i want my
yocto-generated qemu images to take advantage of kvm, i should add the
arg "kvm" to my "runqemu" invocation, is that correct?
if that's the case, might it be worth adding that note to the
standard oe-init-build-env output at the bottom? o
Hi,
I want to throw this out for discussion. I recently was looking at a section
in the YP Reference manual
(http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html#platdev-appdev-devshell)
where it talks about developing using devshell. I asked Darren Hart if this
was
Hi all,
The current Hob allows you to build images for a qemu machine selecting
'live' as your image type. To me (with my pitiful knowledge) this doesn't
make much sense: would I want to deploy an image built for a
virtualisation environment in a real piece of hardware?
So here goes a question: s
On 06/14/2012 02:41 AM, Phil Blundell wrote:
> On Wed, 2012-06-13 at 22:19 -0700, Darren Hart wrote:
>> diff --git a/meta/recipes-core/busybox/busybox.inc
>> b/meta/recipes-core/busybox/busybox.inc
>> index 5b83d32..d07ba7e 100644
>> --- a/meta/recipes-core/busybox/busybox.inc
>> +++ b/meta/reci
Hi.
Many source packages include their own package test suites. We are looking at
running these tests on target in a structured way, and I would like a
discussion about how to best fit this into the Yocto framework.
The actions that need to be performed for a package test are roughly:
1) Build
The OpenSSL recipe halts saying it can't find find.pl however I have
File::Find installed which brings in file.pl as a perl module (find.pm).
Could anyone shed any light on why this might not be found?
Log data follows:
| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python func
Hi all,
Thanks for the feedback: loads of interesting stuff there. We'll keep it all in
mind when working on the next iteration.
If you think of anything else, please post it here.
Cheers
Belen
From: , Jeffrey
mailto:jeffrey.osier-mi...@intel.com>>
Date: Wednesday, 13 June 2012 19:00
To: "St
Hi Darren,
On 14/06/12 01:33, Darren Hart wrote:
> o Do not include the standard Busybox init
...
> o Do not provide inittab functionality
I am not entirely clear what you are hoping to gain by creating a home
grown init solution?
A system that runs nothing but a shell is really not useful for a
30 matches
Mail list logo
