On Sat, Jun 16, 2012 at 08:36:15AM +0200, Martin Jansa wrote:
> On Tue, May 29, 2012 at 05:34:13PM +0200, Martin Jansa wrote:
> > The following changes since commit 44df9dd3dc411ca1255cb4b23bde7eb71aed4778:
> >
> > opkg-make-index: disable filelist by default (2012-04-26 11:39:42 +0100)
>
> pin
On Tue, 2012-05-29 at 17:34 +0200, Martin Jansa wrote:
> The following changes since commit 44df9dd3dc411ca1255cb4b23bde7eb71aed4778:
>
> opkg-make-index: disable filelist by default (2012-04-26 11:39:42 +0100)
>
> are available in the git repository at:
> git://github.com/shr-project/opkg-ut
On Mon, 18 Jun 2012, Tyler Jones wrote:
> Check here: http://www.yoctoproject.org/community/mailing-lists I
> feel that this provides enough of a description of each mailing
> list.
but that list doesn't mention the OE or bitbake mailing lists, for
which some questions will be relevant, no?
rd
"Supported Board Support Packages (BSPs): The Yocto Project provides
a layer called meta-intel and it is maintained in its own separate Git
repository. The meta-intel layer contains many supported BSP
Layers..."
well, yes, but that makes it sound like it's the *only* BSP layer of
any consequenc
Signed-off-by: Robert P. J. Day
---
diff --git a/documentation/dev-manual/dev-manual-intro.xml
b/documentation/dev-manual/dev-manual-intro.xml
index cf5471e..c5a173f 100644
--- a/documentation/dev-manual/dev-manual-intro.xml
+++ b/documentation/dev-manual/dev-manual-intro.xml
@@ -23,7 +23,7 @@
On Mon, Jun 18, 2012 at 10:40 PM, Khem Raj wrote:
>
>
> On Monday, June 18, 2012, James Abernathy wrote:
> >
> >
> > On Mon, Jun 18, 2012 at 5:29 PM, jfabernathy
> wrote:
> >>
> >> On 06/18/2012 05:21 PM, Marc Ferland wrote:
> >>>
> >>> jfabernathy writes:
> >>>
> I needed to do some n
currently in dev manual, link to bitbake doc is:
http://bitbake.berlios.de/manual/
which as you can see is out of date. it's probably worth scanning all
the docs and deciding how to update links for bitbake documentation.
rday
--
===
On Monday 18 June 2012 13:58:03 Jim Rucker wrote:
> I'm trying to build using the code sourcery external compiler and I noticed
> that it's pulling in qemu. This brings up 2 questions-
> 1. Why? Qemu is not a prerequisite for building with GCC and shouldn't be a
> prerequisite for building with CS.
Signed-off-by: Robert P. J. Day
---
diff --git a/documentation/dev-manual/dev-manual-newbie.xml
b/documentation/dev-manual/dev-manual-newbie.xml
index 1f41d1e..9b1636c 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -23,7 +23,
On 18 June 2012 16:04, Björn Stenberg wrote:
> Typically the tests don't mix production and test code, since the purpose is
> to test the production code. Rather the tests are isolated in separate files
> that we relatively easily can build and install separately from the base
> package.
The p
currently, the dev manual (Section 4.2.1) proposes the use of
IMAGE_INSTALL += "strace"
but the poky ref manual in the variable glossary explicitly
discourages that form, and instead recommends
IMAGE_INSTALL_append = " package-name"
can we agree that the "_append" form is preferred? t
@all,
I google some information about this topic and then,
i found the case is that jut support "CodeSourcery labs" toolchain.
I think my external toolchain is not standard of directory like
"tcmode-externl-csl".
I can use "buildroot" to use this toolchian
Good catch Robert. I will take care of this.
Scott
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Robert P. J. Day
Sent: Tuesday, June 19, 2012 3:09 AM
To: Yocto discussion list
Subject: [yocto] links to bitbake info througho
Implemented. Thanks Robert
See http://git.yoctoproject.org/cgit.cgi/yocto-docs/log or
http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html.
Scott
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Robert P. J. Day
On Tue, Jun 19, 2012 at 2:54 AM, James Abernathy wrote:
> You must have missed the earlier discussion. I first got the iperf 2.0.4
> from meta-oe, but wanted 2.0.5, so I just added it to my private collection
> of apps.
you can post the update patch for meta-oe layer
Implemented. Thanks Robert
See http://git.yoctoproject.org/cgit.cgi/yocto-docs/log or
http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html.
Scott
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Robert P. J. Day
Hi all, Please bear with me as I am a newb to both yocto and building
bsp's. I was able to run bitbake core-image-minimal for x86-64, just fine and
run it in qemu.
Then I got gutsy and tried to build a bsp for ARM. Didn't go so well.
I must be missing something.
dallasc ~/development/yocto/p
On Tue, 2012-06-19 at 09:37 -0500, Dallas Clement wrote:
> Hi all, Please bear with me as I am a newb to both yocto and building
> bsp's. I was able to run bitbake core-image-minimal for x86-64, just fine
> and
> run it in qemu.
>
> Then I got gutsy and tried to build a bsp for ARM. Didn't go
Hi Tom,
The first thing I tried is building a minimal distro with "bitbake
core-image-minimal". That completed successfully and I was able to
execute it with qemu.
Then I tried to build a bsp for ARM, which failed with errors shown
earlier. I just tried now for x86_64. It failed too with the s
On Tue, 2012-06-19 at 10:13 -0500, Dallas Clement wrote:
> Hi Tom,
>
> The first thing I tried is building a minimal distro with "bitbake
> core-image-minimal". That completed successfully and I was able to
> execute it with qemu.
>
> Then I tried to build a bsp for ARM, which failed with errors
On Tue, Jun 19, 2012 at 10:20 AM, Khem Raj wrote:
> On Tue, Jun 19, 2012 at 2:54 AM, James Abernathy
> wrote:
> > You must have missed the earlier discussion. I first got the iperf 2.0.4
> > from meta-oe, but wanted 2.0.5, so I just added it to my private
> collection
> > of apps.
>
> you can p
Okay, using the git poky, I was able to build the bsp. It seems that
the tarball version is not able to complete this step:
Getting branches from remote repo git://git.yoctoproject.org/linux-yocto-3.2...
On Tue, Jun 19, 2012 at 10:23 AM, Dallas Clement
wrote:
> That's correct. I have not been
OE and bitbake are tools provided by Yocto Project in Poky. The mailing
lists are not provided or maintained by the Yocto Project thus them not
being on the Yocto Project's site. You could make a wiki page,
https://wiki.yoctoproject.org/wiki/Mailing_Lists, with the mailing lists
and their descripti
On 19 June 2012 02:29, Robert P. J. Day wrote:
>
> "Supported Board Support Packages (BSPs): The Yocto Project provides
> a layer called meta-intel and it is maintained in its own separate Git
> repository. The meta-intel layer contains many supported BSP
> Layers..."
>
> well, yes, but that mak
On Tue, 2012-06-19 at 10:29 -0500, Dallas Clement wrote:
> Okay, using the git poky, I was able to build the bsp. It seems that
> the tarball version is not able to complete this step:
>
> Getting branches from remote repo
> git://git.yoctoproject.org/linux-yocto-3.2...
>
OK, glad that the git
On Tuesday 19 June 2012 08:22:00 Robert P. J. Day wrote:
> currently, the dev manual (Section 4.2.1) proposes the use of
>
> IMAGE_INSTALL += "strace"
>
> but the poky ref manual in the variable glossary explicitly
> discourages that form, and instead recommends
>
> IMAGE_INSTALL_append =
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 a
On 19 Jun 2012, at 18:52, Paul Eggleton wrote:
> On Tuesday 19 June 2012 08:22:00 Robert P. J. Day wrote:
>> currently, the dev manual (Section 4.2.1) proposes the use of
>>
>> IMAGE_INSTALL += "strace"
>>
>> but the poky ref manual in the variable glossary explicitly
>> discourages that form,
Hello,
I submit to your attention the following issue related to Yocto project's
bugzilla:
Which is the most appropriate end for a the lifecycle of a bugzilla issue:
VERIFIED or CLOSED?
Currently the bug lifecycle final point is VERIFIED and the status CLOSED is
not used. Setting a bug to CLOS
On Tuesday, June 19, 2012, Serban, Laurentiu
wrote:
> Hello,
>
>
>
> I submit to your attention the following issue related to Yocto project’s
bugzilla:
>
>
>
> Which is the most appropriate end for a the lifecycle of a bugzilla
issue: VERIFIED or CLOSED?
>
> Currently the bug lifecycle final poin
Attendees:
Darren, Beth, Saul, Tom, Jessica, LaurentiuS, Scott Garman, Richard, Nitin,
ScottR, Michael, Paul, Jim, Bjorn (Enea), Ross, Jefro, Bogdan, Gilbert, Jeff,
Sahad, Sean, Cristian, Alex, Bruce, Josh, Song
Agenda:
* Opens collection - 5 min (Song)
* 1.2.1 update - 5 min (ScottG)
- 1 r
I'm experiencing some grief trying to run hob from my Debian Squeeze (6.0.5).
[dallasc /development/dallasc/yocto/poky/build] hob
FATAL: Gtk+, PyGtk and PyGobject are required to use Hob,
You have Gtk+ 2.20.1 and PyGtk 2.17.0.
I believe I have all these packages installed. Perhaps it needs newer
On 06/19/2012 12:25 PM, Serban, Laurentiu wrote:
> Hello,
>
>
>
> I submit to your attention the following issue related to Yocto
> project’s bugzilla:
>
>
>
> Which is the most appropriate end for a the lifecycle of a bugzilla
> issue: VERIFIED or CLOSED?
>
> Currently the bug lifecycle
On 19/06/12 15:31, Dallas Clement wrote:
I'm experiencing some grief trying to run hob from my Debian Squeeze (6.0.5).
[dallasc /development/dallasc/yocto/poky/build] hob
FATAL: Gtk+, PyGtk and PyGobject are required to use Hob,
You have Gtk+ 2.20.1 and PyGtk 2.17.0.
This would be much more us
Is anybody using devshell actively who can recreate this section of
bitbake.conf?
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Rifenbark, Scott M
Sent: Tuesday, June 19, 2012 11:14 AM
To: Yocto discussion list
Subject: [yocto] developing with devshell
I have a cross-toolchain supplied by an ARM SoC vendor which I need to
use to build my distro. What is required to use a toolchain like this
instead of one of the yocto cross-toolchain tarballs?
Thanks
___
yocto mailing list
yocto@yoctoproject.org
https
On Tue, Jun 19, 2012 at 9:28 PM, Dallas Clement
wrote:
> I have a cross-toolchain supplied by an ARM SoC vendor which I need to
> use to build my distro. What is required to use a toolchain like this
> instead of one of the yocto cross-toolchain tarballs?
>
I answered this question just today fo
Hi Scott,
On 19/06/12 19:13, Rifenbark, Scott M wrote:
> 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 d
Hi,
On 19/06/12 19:47, Chris Tapp wrote:
> Is there a section that explains the order in which all these things
> happen? i.e. items in local.conf happen before/after...
IIRC, the evaluation orders is:
1. variables on the command line (e.g., 'MACHINE=beagleboard bitbake
myimage') are evaluated f
39 matches
Mail list logo
