On 05/09/12 22:46, Richard Purdie wrote:
> On Tue, 2012-09-04 at 09:58 +0100, Tomas Frydrych wrote:
>> Hi Bruce,
>>
>> On 03/09/12 22:08, Bruce Ashfield wrote:
>>> That being said, taking a step back, what are you trying to get out of
>>> meta-yocto in this scenario ?
>>
>> a) I am targeting multi
On 05/09/12 22:56, Jack Mitchell wrote:
> On 05/09/2012 22:46, Paul Eggleton wrote:
>> On Wednesday 05 September 2012 12:16:44 Gary Thomas wrote:
>>> I just built Yocto/Poky for the raspberrypi, following the
>>> recent thread on this list. I noticed that the resulting SD
>>> image is ~4GB, but mo
On Wednesday 05 September 2012 22:57:22 Jack Mitchell wrote:
> On 05/09/2012 22:46, Paul Eggleton wrote:
> > On Wednesday 05 September 2012 12:16:44 Gary Thomas wrote:
> >> Also, is it possible to just build the SD image much like I do for
> >> other devices like the BeagleBoard, albeit with differ
On Tue, 2012-09-04 at 09:21 +0100, Jack Mitchell wrote:
> On 03/09/12 22:08, Bruce Ashfield wrote:
> > On Mon, Sep 3, 2012 at 4:55 PM, Tomas Frydrych
> > wrote:
> >> snip...
> >>
> >>
> >>
> >> That being said, taking a step back, what are you trying to get out of
> >> meta-yocto in this scenario
On 05/09/2012 22:46, Paul Eggleton wrote:
On Wednesday 05 September 2012 12:16:44 Gary Thomas wrote:
I just built Yocto/Poky for the raspberrypi, following the
recent thread on this list. I noticed that the resulting SD
image is ~4GB, but most of that space seems to be unused:
$ ssh root@1
Hi
I need to add a new environment that LD_LIBRARY_PATH when I use my own
external toolchain .
I add 1 line in external-toolchain.inc "LD_LIBRARY_PATH =.
"${EXTERNAL_TOOLCHAIN}/i586-target-linux-gnu/lib:"",but there is no effect.when
I used this toolchain to compile , there als
On 04/09/12 09:43, Jack Mitchell wrote:
On 03/09/12 22:00, Tomas Frydrych wrote:
Hi Jack,
On 03/09/12 18:52, Jack Mitchell wrote:
As some of you know I run a small Raspberry Pi community site[1] and I
would like to write a follow up to an earlier blog post about preparing
yourself for programm
On 05/09/2012 22:46, Paul Eggleton wrote:
On Wednesday 05 September 2012 12:16:44 Gary Thomas wrote:
I just built Yocto/Poky for the raspberrypi, following the
recent thread on this list. I noticed that the resulting SD
image is ~4GB, but most of that space seems to be unused:
$ ssh root@1
On 05/09/2012 18:13, Trevor Woerner wrote:
I also found that I had to add:
BB_DANGLINGAPPENDS_WARNONLY = "yes"
at the end of my conf/local.conf since I received a:
ERROR: No recipes available for:
/home/trevor/devel/yocto/raspi/poky/meta-raspberrypi/recipes-multimedia/libav/l
On Wed, 2012-09-05 at 10:20 -0400, William Mills wrote:
> On 09/04/2012 07:23 PM, Darren Hart wrote:
> >
> >
> > On 09/04/2012 01:25 PM, William Mills wrote:
> >
> >> Darren: Is it true you can't get @ the Intel BSP's w/o also getting the
> >> poky distro defs? That does seem to mixing things a bi
On Tue, 2012-09-04 at 09:58 +0100, Tomas Frydrych wrote:
> Hi Bruce,
>
> On 03/09/12 22:08, Bruce Ashfield wrote:
> > That being said, taking a step back, what are you trying to get out of
> > meta-yocto in this scenario ?
>
> a) I am targeting multiple chips, including TI Omap and Intel Atom.
>
On Wednesday 05 September 2012 12:16:44 Gary Thomas wrote:
> I just built Yocto/Poky for the raspberrypi, following the
> recent thread on this list. I noticed that the resulting SD
> image is ~4GB, but most of that space seems to be unused:
>
>$ ssh root@192.168.1.150
>Warning: Permanent
On Wed, 2012-09-05 at 13:48 +0100, Richard Purdie wrote:
> The root of the problem is that meta-yocto mixes up policy and hardware
> support which is bad. It also means its not compliant with the new Yocto
> Project compliance criteria and hence is not Yocto Project Compatible.
>
> Now we've got t
On Wed, 2012-09-05 at 09:56 -0700, Saul Wold wrote:
> The following changes since commit 16a7879b98352b70e8c17181912a26212d716c87:
>
> meta-emenlow: rename recipes-gnome bbappends (2012-09-04 10:04:37 -0500)
>
> are available in the git repository at:
> git://git.yoctoproject.org/poky-contrib
On Wed, 2012-09-05 at 09:56 -0700, Saul Wold wrote:
> Signed-off-by: Saul Wold
Acked-by: Tom Zanussi
> ---
> .../recipes-core/psplash/files/psplash-tlk.png | Bin 0 -> 42295 bytes
> meta-tlk/recipes-core/psplash/psplash_git.bbappend | 10 ++
> 2 files changed, 10 insertions(+),
On Wed, 2012-09-05 at 09:56 -0700, Saul Wold wrote:
> Signed-off-by: Saul Wold
Acked-by: Tom Zanussi
> ---
> .../recipes-kernel/linux/linux-yocto_3.0.bbappend |2 ++
> .../recipes-kernel/linux/linux-yocto_3.2.bbappend |6 ++
> .../recipes-kernel/linux/linux-yocto_3.4.bbappend |
On Wed, 2012-09-05 at 09:56 -0700, Saul Wold wrote:
> Signed-off-by: Saul Wold
Acked-by: Tom Zanussi
> ---
> .../base-files/base-files_3.0.14.bbappend |3 +++
> meta-tlk/recipes-core/base-files/files/motd|7 +++
> 2 files changed, 10 insertions(+), 0 deletions(-)
>
On Tue, Sep 04, 2012 at 09:18:43PM -0700, Saul Wold wrote:
> On 09/04/2012 02:00 PM, Martin Jansa wrote:
> > On Tue, Sep 04, 2012 at 01:57:19PM -0700, Saul Wold wrote:
> >> Signed-off-by: Saul Wold
> >> ---
> >> .../recipes-kernel/linux/linux-yocto_3.0.bbappend |2 ++
> >> .../recipes-kern
On Wed, Sep 05, 2012 at 01:48:23PM +0100, Richard Purdie wrote:
> On Wed, 2012-09-05 at 10:43 +0100, Tomas Frydrych wrote:
> > On 05/09/12 10:15, Paul Eggleton wrote:
> > > On Wednesday 05 September 2012 09:49:11 Tomas Frydrych wrote:
> > > It has been considered witin OE to be best practice to app
On Wed, Sep 5, 2012 at 12:06 PM, Bruce Ashfield
wrote:
> On 12-09-05 03:03 PM, Khem Raj wrote:
>>
>> On Wed, Sep 5, 2012 at 11:16 AM, Saul Wold wrote:
>>>
>>> This is to prevent the HW BSP generated by the autobuild from being used
>>> in
>>> production, it's added by the autobuilder to the HW bs
On 05/09/12 20:03, James Macon wrote:
> I found it but this is only partially the answer. I found
> PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto" in qemu.inc but there
> is no recipe for linux-yocto. There are recipes for linux-yocto_3.* ,
> linux-yocto-tiny, and linux-yocto-rt_3*.
>
> So
On 12-09-05 03:03 PM, Khem Raj wrote:
On Wed, Sep 5, 2012 at 11:16 AM, Saul Wold wrote:
This is to prevent the HW BSP generated by the autobuild from being used in
production, it's added by the autobuilder to the HW bsps.
thats fine. However, I am using linux-yocto unmodified from meta-yocto
I found it but this is only partially the answer. I found
PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto" in qemu.inc but there
is no recipe for linux-yocto. There are recipes for linux-yocto_3.* ,
linux-yocto-tiny, and linux-yocto-rt_3*.
Somewhere during the build process something is appe
On Wed, Sep 5, 2012 at 11:16 AM, Saul Wold wrote:
> This is to prevent the HW BSP generated by the autobuild from being used in
> production, it's added by the autobuilder to the HW bsps.
thats fine. However, I am using linux-yocto unmodified from meta-yocto
so this will now
force me to generate
Sorry for the late. Forgot to hit the sent button yesterday.
Attendees:
Alex, MichaelH, Cristian, Darren, Tom, LaurentiuP, Nitin, Bjorn, BogdanM,
Bruce, Sean, Dave, Paul, Saul, Richard, LaurentiuS, Cristiana, Ross, ScottR
Agenda:
* Opens collection - 5 min (Song)
* Yocto 1.3 status - 10 min
On 09/05/2012 10:43 AM, Khem Raj wrote:
On Wed, Sep 5, 2012 at 10:15 AM, Saul Wold wrote:
It will add another .1 to the PR, if PR = 4.1, it will become 4.1.1
sorry, I was more interested in the time limited kernel option.
Sorry, you had put that right under the PR line and JaMa had also
I just built Yocto/Poky for the raspberrypi, following the
recent thread on this list. I noticed that the resulting SD
image is ~4GB, but most of that space seems to be unused:
$ ssh root@192.168.1.150
Warning: Permanently added '192.168.1.150' (RSA) to the list of known hosts.
root@192.16
On 5 September 2012 18:13, Trevor Woerner wrote:
> I also found that I had to add:
>
> BB_DANGLINGAPPENDS_WARNONLY = "yes"
>
> at the end of my conf/local.conf since I received a:
>
> ERROR: No recipes available for:
>
> /home/trevor/devel/yocto/raspi/poky/meta-raspberrypi/recipes-m
On Wed, Sep 5, 2012 at 10:15 AM, Saul Wold wrote:
>
>
> It will add another .1 to the PR, if PR = 4.1, it will become 4.1.1
sorry, I was more interested in the time limited kernel option.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yocto
Hi,
On 05/09/12 18:35, James Macon wrote:
> I successfully built core-image-minimal. I now what to understand how the
> build determine what linux kernel it will be using because the next step I
> will want to do is add my own recipe that references my own kernel. I
> have not been able to fi
I successfully built core-image-minimal. I now what to understand how the
build determine what linux kernel it will be using because the next step I
will want to do is add my own recipe that references my own kernel. I
have not been able to find where the linkage to specific kernel is. Can
so
On 09/05/2012 10:08 AM, Khem Raj wrote:
On Wed, Sep 5, 2012 at 9:56 AM, Saul Wold wrote:
Signed-off-by: Saul Wold
---
.../recipes-kernel/linux/linux-yocto_3.0.bbappend |2 ++
.../recipes-kernel/linux/linux-yocto_3.2.bbappend |6 ++
.../recipes-kernel/linux/linux-yocto_3.4.bba
I also found that I had to add:
BB_DANGLINGAPPENDS_WARNONLY = "yes"
at the end of my conf/local.conf since I received a:
ERROR: No recipes available for:
/home/trevor/devel/yocto/raspi/poky/meta-raspberrypi/recipes-multimedia/libav/libav_0.7.4.bbappend
the first time I tried baki
On Wed, Sep 5, 2012 at 9:56 AM, Saul Wold wrote:
> Signed-off-by: Saul Wold
> ---
> .../recipes-kernel/linux/linux-yocto_3.0.bbappend |2 ++
> .../recipes-kernel/linux/linux-yocto_3.2.bbappend |6 ++
> .../recipes-kernel/linux/linux-yocto_3.4.bbappend |6 ++
> 3 files chan
Signed-off-by: Saul Wold
---
.../recipes-core/psplash/files/psplash-tlk.png | Bin 0 -> 42295 bytes
meta-tlk/recipes-core/psplash/psplash_git.bbappend | 10 ++
2 files changed, 10 insertions(+), 0 deletions(-)
create mode 100644 meta-tlk/recipes-core/psplash/files/psplash-tlk.png
Signed-off-by: Saul Wold
---
.../recipes-kernel/linux/linux-yocto_3.0.bbappend |2 ++
.../recipes-kernel/linux/linux-yocto_3.2.bbappend |6 ++
.../recipes-kernel/linux/linux-yocto_3.4.bbappend |6 ++
3 files changed, 14 insertions(+), 0 deletions(-)
create mode 100644 meta
The following changes since commit 16a7879b98352b70e8c17181912a26212d716c87:
meta-emenlow: rename recipes-gnome bbappends (2012-09-04 10:04:37 -0500)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib sgw/meta-tlk
http://git.yoctoproject.org/cgit.cgi/poky-contri
Signed-off-by: Saul Wold
---
.../base-files/base-files_3.0.14.bbappend |3 +++
meta-tlk/recipes-core/base-files/files/motd|7 +++
2 files changed, 10 insertions(+), 0 deletions(-)
create mode 100644 meta-tlk/recipes-core/base-files/base-files_3.0.14.bbappend
create
On Wed, 2012-09-05 at 10:45 -0400, William Mills wrote:
>
> On 09/05/2012 08:48 AM, Richard Purdie wrote:
> > On Wed, 2012-09-05 at 10:43 +0100, Tomas Frydrych wrote:
> >> On 05/09/12 10:15, Paul Eggleton wrote:
> >>> On Wednesday 05 September 2012 09:49:11 Tomas Frydrych wrote:
> >>> It has been
On 05/09/12 16:20, Trevor Woerner wrote:
On Wed, Sep 5, 2012 at 5:58 AM, Jack Mitchell wrote:
This is now livefor anyone interested.
http://www.pimpmypi.com/blog/blogPost.php?blogPostID=7
Shouldn't the instructions include a step adding the meta-raspberrypi
layer to conf/bblayers.conf?
Well
On Wed, Sep 5, 2012 at 5:58 AM, Jack Mitchell wrote:
> This is now livefor anyone interested.
> http://www.pimpmypi.com/blog/blogPost.php?blogPostID=7
Shouldn't the instructions include a step adding the meta-raspberrypi
layer to conf/bblayers.conf?
___
On 12-09-05 10:20 AM, William Mills wrote:
On 09/04/2012 07:23 PM, Darren Hart wrote:
On 09/04/2012 01:25 PM, William Mills wrote:
Darren: Is it true you can't get @ the Intel BSP's w/o also getting the
poky distro defs? That does seem to mixing things a bit. (I am not
claiming meta-ti is cl
On 05/09/12 15:45, William Mills wrote:
>> Its accepted that most layers will append to BBPATH. I do think its
>> acceptable for a distro policy layer to prepend though and this is why
>> meta-yocto does this. I don't remember the exact reason right now but
>> the principle stands.
>
> So how shou
On 09/05/2012 08:48 AM, Richard Purdie wrote:
On Wed, 2012-09-05 at 10:43 +0100, Tomas Frydrych wrote:
On 05/09/12 10:15, Paul Eggleton wrote:
On Wednesday 05 September 2012 09:49:11 Tomas Frydrych wrote:
It has been considered witin OE to be best practice to append to BBPATH and
not prepend,
On 09/05/2012 07:20 AM, William Mills wrote:
> On 09/04/2012 07:23 PM, Darren Hart wrote:
>>
>>
>> On 09/04/2012 01:25 PM, William Mills wrote:
>>
>>> Darren: Is it true you can't get @ the Intel BSP's w/o also getting the
>>> poky distro defs? That does seem to mixing things a bit. (I am not
>
On 09/05/2012 02:15 AM, Paul Eggleton wrote:
> On Wednesday 05 September 2012 09:49:11 Tomas Frydrych wrote:
>> The simplest fix would be for meta-ti to preppend itself to the path the
>> same way meta-yocto does, i.e., in the layer.conf
>>
>> BBPATH := "${LAYERDIR}:${BBPATH}"
>>
>> In fact, th
Signed-off-by: Paul Eggleton
---
documentation/poky-ref-manual/ref-classes.xml | 28 +++--
1 file changed, 26 insertions(+), 2 deletions(-)
diff --git a/documentation/poky-ref-manual/ref-classes.xml
b/documentation/poky-ref-manual/ref-classes.xml
index b836e2c..9e07c62 100
Add a short section about packagegroup.bbclass.
Signed-off-by: Paul Eggleton
---
documentation/poky-ref-manual/ref-classes.xml | 22 +-
1 file changed, 21 insertions(+), 1 deletion(-)
diff --git a/documentation/poky-ref-manual/ref-classes.xml
b/documentation/poky-ref-manu
* For PE/PV/PR/PN these pertain to a recipe ("package" was used here
historically).
* References to variables should not be prefixed with $ in the text
* Add text about suffixing RCONFLICTS as per other package variables
* Make ALLOW_EMPTY example complete
* Clarify and add example for AUTOREV
S
Update the BitBake "Preferences and Providers" section to remove
references to these two Pimlico applications that have been removed,
and tweak the example slightly so it is technically correct.
Signed-off-by: Paul Eggleton
---
documentation/poky-ref-manual/ref-bitbake.xml |8
1 fil
List frameworks we provide that are likely to be used by people these
days - Pimlico has been removed and GuPNP and Matchbox don't really
belong. Also slightly modify the sentence following so that it is clear
that these are optional.
Signed-off-by: Paul Eggleton
---
.../yocto-project-qs/yocto-p
* core-image-core was renamed to core-image-x11 and the editor and file
manager were removed.
* core-image-basic's description has been updated to reflect its
intended purpose
* core-image-lsb is intended to be standalone - should not be
associated with core-image-basic.
* The Pimlico applica
Also add a definition for PACKAGE_BEFORE_PN since the default value of
PACKAGES now includes this.
Signed-off-by: Paul Eggleton
---
documentation/poky-ref-manual/ref-variables.xml |9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/documentation/poky-ref-manual/ref-var
These file paths are no longer valid, instead point to the section
of the reference manual with more information on valid IMAGE_FEATURES.
Signed-off-by: Paul Eggleton
---
documentation/poky-ref-manual/ref-variables.xml |9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git
* apps-console-core has been effectively replaced by splash
* apps-x11-core, apps-x11-games have been removed
* ssh-server-* were added quite a while ago, add these here
* x11 has been added
* x11-base has changed behaviour slightly
* doc-pkgs was added
* nfs-server never exported the entire /, so
Task has been renamed to package group, and there are some minor changes
in how package group recipes should be constructed - in particular the
inherit of packagegroup.bbclass is now highly recommended as it will set
appropriate defaults and automatically add complementary -dev and -dbg
packages.
Signed-off-by: Paul Eggleton
---
documentation/poky-ref-manual/ref-bitbake.xml |2 +-
documentation/poky-ref-manual/ref-variables.xml |8
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/documentation/poky-ref-manual/ref-bitbake.xml
b/documentation/poky-ref-manua
The meta-intel BSPs and yocto-bsp tool no longer use a bbappend of
task-core-tools-profile to add systemtap, so these sections should be
removed.
Signed-off-by: Paul Eggleton
---
documentation/bsp-guide/bsp.xml| 24
.../dev-manual/dev-manual-bsp-appendix.xm
Documentation fixes for the recent package group changes as well
as a few other things I noticed along the way.
The following changes since commit 12f77236b602e9ec43e845c8cec060ad342af19c:
documentation: Fixed links to BitBake User Manual (2012-09-04 12:05:21 -0700)
are available in the git r
On 09/04/2012 07:23 PM, Darren Hart wrote:
On 09/04/2012 01:25 PM, William Mills wrote:
Darren: Is it true you can't get @ the Intel BSP's w/o also getting the
poky distro defs? That does seem to mixing things a bit. (I am not
claiming meta-ti is clean yet but I want to understand the Intel
On Wed, 2012-09-05 at 10:43 +0100, Tomas Frydrych wrote:
> On 05/09/12 10:15, Paul Eggleton wrote:
> > On Wednesday 05 September 2012 09:49:11 Tomas Frydrych wrote:
> > It has been considered witin OE to be best practice to append to BBPATH and
> > not prepend, the thinking being that then the sea
- @Override annotations can be used starting with jre >= 1.6
- Headless build plugin limited the java compilation to 1.5 (no matter what the
system jdk is)
Signed-off-by: Ioana Grigoropol
---
.../org.yocto.sdk.headless.build/build.properties |4 ++--
.../sdk/remotetools/wizards/bsp/MainPag
On 03/09/12 22:00, Tomas Frydrych wrote:
Hi Jack,
On 03/09/12 18:52, Jack Mitchell wrote:
As some of you know I run a small Raspberry Pi community site[1] and I
would like to write a follow up to an earlier blog post about preparing
yourself for programming on the Raspberry Pi with the Yocto Pr
On 05/09/12 10:15, Paul Eggleton wrote:
> On Wednesday 05 September 2012 09:49:11 Tomas Frydrych wrote:
> It has been considered witin OE to be best practice to append to BBPATH and
> not prepend, the thinking being that then the search path matches the order
> of
> the layers listed in bblayers
On Wednesday 05 September 2012 09:49:11 Tomas Frydrych wrote:
> The simplest fix would be for meta-ti to preppend itself to the path the
> same way meta-yocto does, i.e., in the layer.conf
>
> BBPATH := "${LAYERDIR}:${BBPATH}"
>
> In fact, this is the *only* way that a layer can override any co
On 04/09/12 21:25, William Mills wrote:
> I suspect the current issue is just growing pains for a case that has
> not been tested.
The simplest fix would be for meta-ti to preppend itself to the path the
same way meta-yocto does, i.e., in the layer.conf
BBPATH := "${LAYERDIR}:${BBPATH}"
In fa
66 matches
Mail list logo
