Here is a link to draft section on the user configuration block of the YP
Development Environment work. Check this out and provide feedback for
appropriate level of detail, usefulness, missing info, ect. This draft
section, once we settle on it, will set the tone and level for the remaining
d
On 13-07-08 11:16 AM, Paul Eggleton wrote:
On Friday 28 June 2013 14:36:48 Khem Raj wrote:
On Jun 28, 2013, at 4:22 AM, "Rifenbark, Scott M"
wrote:
I count eight meta-* layers in the YP repositories that don't exist in the
OE area. I understand what you are saying though and I can word it tha
Hi Thanassis - if there is no reply here, you might try joining and
posting on the meta-freescale mailing list
(https://lists.yoctoproject.org/listinfo/meta-freescale)
On Thu, Jul 4, 2013 at 7:24 AM, Thanassis Silis wrote:
>
>
>
> From: djnass...@hotmail.com
> To:
Agenda:
* Opens collection - 5 min (Song)
* Yocto 1.5 status - 10 min (Song/team)
https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.5_Status
* SWAT team rotation: Ioana -> Laurentiu Palcu
* Opens - 10 min
* Team Sharing - 20 min
-Original Appointment-
We encourage people attending
> From: Tomas Frydrych
>
> On 06/07/13 02:23, Paul D. DeRocco wrote:
> > Does anyone know what recipe actually sets LABELS?
>
> The relevant image classes do.
Thanks. It turned out to be image-live.bbclass, which sets a bunch of
SYSLINUX_xxx symbols unless they've already been set, and which are
Thanks Alexandru.
I will try the headless build. I wonder if there is an install log in
eclipse showing the list of missing components.
Norman
On Mon, Jul 8, 2013 at 6:48 AM, Georgescu, Alexandru C <
alexandru.c.george...@intel.com> wrote:
> Hi Norman,
>
> There may be some items that you hav
This mail was sent out by Package Report System.
It will list all the recipes which can't check upstream version by script, and
will show how long it is since their last mannual version check.
You can check the detail information at
http://packages.yoctoproject.org/manuallychkinfo
PackageName
This mail was sent out by Package Report System.
This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade this time, they can fill in
RECIPE_NO_UPDATE_REASON_pn-"xxx" in upstream_tracking files to ignore this
recipe remainder until newer u
T_SYS= "arm-poky-linux-gnueabi"
MACHINE = "beagleboard"
DISTRO = "poky"
DISTRO_VERSION= "1.4+snapshot-20130708"
TUNE_FEATURES = "armv7a vfp neon"
TARGET_FPU= "vfp-neon"
meta
meta-yo
On 8 July 2013 16:02, Barros Pena, Belen wrote:
> There seem to be certain rules regarding .bb files naming, but apparently
> those are not written anywhere. Some of those rules seem to be:
>
> * No spaces
> * Underscores can only by used to separate name and version
> * No ASCII special character
On 8 July 2013 16:02, Andrei Gherzan wrote:
> recipes-core-ivi/busybox/busybox-1.20.2/defconfig | 1012
> -
> recipes-core-ivi/busybox/busybox-1.21.1/defconfig | 1012
> +
I'm curious as to what IVI needs tweaked in busybox and why this can't
go into oe-c
On Friday 28 June 2013 14:36:48 Khem Raj wrote:
> On Jun 28, 2013, at 4:22 AM, "Rifenbark, Scott M"
> wrote:
> > I count eight meta-* layers in the YP repositories that don't exist in the
> > OE area. I understand what you are saying though and I can word it that
> > way to dampen the existence o
Bug 4193 will allow Hob users to save their customised images into a .bb
file. As part of the saving flow, users will need to give their .bb file a
name, and we need to ensure such names are valid.
There seem to be certain rules regarding .bb files naming, but apparently
those are not written anyw
Signed-off-by: Andrei Gherzan
---
recipes-qt/qt4/qt4-embedded_4.8.4.bbappend | 24
recipes-qt/qt4/qt4-embedded_4.8.5.bbappend | 24
2 files changed, 24 insertions(+), 24 deletions(-)
delete mode 100644 recipes-qt/qt4/qt4-embedded_4.8.4.bbappe
nstalled with rpm -Uh --force
> make-3.81-19.fc13.x86_64.rpm
> MACHINE=beagleboard bitbake core-image-sato-sdk-ex is currently
> working.
>
> Build Configuration:
> BB_VERSION= "1.19.1"
> BUILD_SYS = "x86_64-linux"
> NATI
> so -- short form of the question -- how many ways are there to build
> a bootable SD card for the BBB using different layers?
There are many ways to skin a cat. I created my own BeagleBone BSP layer
that builds u-boot and a 3.2 kernel. The idea being to demonstrate how to
create a BSP layer.
3.x86_64.rpm
MACHINE=beagleboard bitbake core-image-sato-sdk-ex is currently working.
Build Configuration:
BB_VERSION= "1.19.1"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Fedora-18"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE
Hi Norman,
There may be some items that you have missed, or you can try another way by
running a headless build and then trying to install the plugin. The headless
build should be able to install the required items needed by the plugin.
To run the headless build, you have to have the eclipse-po
Re-sending as we've hit another rash of these issues and it ate up a couple
days of investigation that still led to no resolution or figuring out how
to reproduce it. I'm going to log a bug in a day or so, even though my
information is incomplete, if no one knows what's going on here and can
expla
On 8 July 2013 10:01, Tomas Frydrych wrote:
> On 06/07/13 12:22, Paul Barker wrote:
>>
>> Does anyone else who's worked with meta-raspberrypi agree with this?
>> If so I'll throw together patches to achieve this.
>
> vc-graphics is the original package before the userland sources were
> made avail
Am 11.04.2013 15:19, schrieb Jonas Jonsson L:
> The package that I’ve built builds clean without any warnings in the
> ‘clean’ build. However, if I _don’t_ build my package in the clean
> image, but in one of my ‘configured’ images, it fails. All of a sudden,
> the linker can’t find neither /lib
On 06/07/13 02:23, Paul D. DeRocco wrote:
> Does anyone know what recipe actually sets LABELS?
The relevant image classes do.
Tomas
--
http://sleepfive.com
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On 06/07/13 12:22, Paul Barker wrote:
> So if there recipes are fulfilling the exact same purpose, I think we
> should strip out vc-graphics completely and always build from source.
> I've never seen a use case for the pre-compiled vc-graphics recipes
> within OpenEmbedded/Yocto.
>
> Does anyone e
Hi Michael,
For the rc1, we have advanced with Fullpass testing so I think it's best that
we continue with it than stop, and have another RC this week.
Regards,
--
Alexandru Georgescu
From: Michael Halstead [mailto:mhalst...@linuxfoundation.org] On Behalf Of
Michael Halstead
Sent: Friday, Ju
24 matches
Mail list logo
