The weekly build is built and available at:
http://autobuilder.yoctoproject.org/pub/nightly/20130403-2
Known issues:
Due to Bug 4186 - bitbake package-index fails over NFS, the adt-ipk
package index was created and deployed by hand. I have a temp fix in
the autobuilder to work around this issue
On 13-04-03 6:16 PM, Darren Hart wrote:
Enable meta-kernel-dev support for the 3.8 kernels.
Acked-by: Bruce Ashfield
I have something similar local to my machine that I hadn't gotten
around to pushing out.
Cheers,
Bruce
Signed-off-by: Darren Hart
---
.../linux/linux-yocto-rt_3.8.bbappe
> From: Bodke, Kishore K
>
> It's surprising that you don't see anything under
> /home/pauld/yocto-atom/build/tmp/work/cedartrail_nopvr-poky-li
nux/linux-yoct
> o-3.0.32+git1+a4ac64fe873f08ef718e2849b88914725dc99c1c_1+1e79e
03d115ed177882
> ab53909a4f3555e434833-r4.1/linux-cedartrail-nopvr-standa
> From: Darren Hart
>
> Are you building with the rm work setting? Otherwise, that
> should not be
> empty unless you have more than one linux-yocto* directory
> and the other
> is populated.
>
> If not, verify rm work is not on and just build the kernel:
>
> $ bitbake linux-yocto -c cleanssta
> I'm starting w/ an SDK based on yocto & am trying to add canutil to the build.
> There's already a recipe in meta-oe, but unfortunately I can't get through my
> corporate firewall w/ the git protocol. However I can w/ http. So I added a
> layer
> w/ a bbppend to change the SRC_URI
Alternatively
Enable meta-kernel-dev support for the 3.8 kernels.
Signed-off-by: Darren Hart
---
.../linux/linux-yocto-rt_3.8.bbappend | 25
.../recipes-kernel/linux/linux-yocto_3.8.bbappend | 25
2 files changed, 50 insertions(+), 0 deletions(-)
cr
On 04/03/2013 01:50 PM, Paul D. DeRocco wrote:
>> From: Darren Hart [mailto:dvh...@linux.intel.com]
>>
>> Are you building with the rm work setting? Otherwise, that
>> should not be
>> empty unless you have more than one linux-yocto* directory
>> and the other is populated.
>
> That option is
>-Original Message-
>From: yocto-boun...@yoctoproject.org [mailto:yocto-
>boun...@yoctoproject.org] On Behalf Of Paul D. DeRocco
>Sent: Wednesday, April 03, 2013 1:50 PM
>To: 'Darren Hart'
>Cc: yocto@yoctoproject.org
>Subject: Re: [yocto] This one can't be me...
>
>> From: Darren Hart [ma
> From: Darren Hart [mailto:dvh...@linux.intel.com]
>
> Are you building with the rm work setting? Otherwise, that
> should not be
> empty unless you have more than one linux-yocto* directory
> and the other is populated.
That option is off, and there is no other linux-yocto* directory.
> If
On 04/03/2013 12:57 PM, Paul D. DeRocco wrote:
>> From: Darren Hart
>>
>> The most obvious question is whether or not the kernel you built has
>> ramdisk support. You can do this by analyzing the .config file in your
>> linux-yocto build tree
>> (build/tmp/work/cedartrail.../linux-yocto*/linux-ce
On 13-04-03 03:49 AM, Hongxu Jia wrote:
The following changes since commit 1b534b2f8bbe9b8a773268cfa30a4850346f6f5f:
meta: preempt-rt, inherit standard config (2013-03-25 13:36:42 -0700)
Thanks for the change.
I've staged the change locally, I'll have it pushed out in the
next day or so.
> From: Darren Hart
>
> The most obvious question is whether or not the kernel you built has
> ramdisk support. You can do this by analyzing the .config file in your
> linux-yocto build tree
> (build/tmp/work/cedartrail.../linux-yocto*/linux-cedartrail-st
> andard-build/.config).
> You want to look
On 3 April 2013 19:52, Saridakis, Dean (US SSA)
wrote:
> from
> "git://git.pengutronix.de/git/tools/canutils.git;protocol=git;tag=${TAG}"
>
> to
> "http://git.pengutronix.de/git/tools/canutils.git;protocol=http;tag=${TAG}”
Don't change the leading git: to http:, as then you're not using the
git
I've got the yocto basics, but sill a novice.
I'm starting w/ an SDK based on yocto & am trying to add canutil to the build.
There's already a recipe in meta-oe, but unfortunately I can't get through my
corporate firewall w/ the git protocol. However I can w/ http. So I added a
layer w/ a bbppe
Hi Paul,
We removed clutter project templates just because we found that the underline
package support for it is no longer there(in core-image-sato) and assume that
there's a reason for the change. I'm in the same boat as you that by no means
I'm an expert with clutter thus don't know how popu
Signed-off-by: Paul Eggleton
---
documentation/dev-manual/dev-manual-common-tasks.xml |3 +++
1 file changed, 3 insertions(+)
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml
b/documentation/dev-manual/dev-manual-common-tasks.xml
index a697b8c..66df375 100644
--- a/document
* BBFILES should be appended to with +=
* BBPATH should be appended to with .=
* Immediate expansion is not necessary for BBFILE_PRIORITY
* Immediate expansion is not necessary for references in layer.conf
to LAYERDIR since these are automatically expanded at the end of
parsing the file (and ha
Add a paragraph to the top of the section on buildhistory mentioning the
metadata-revs file and the top-level directories.
Signed-off-by: Paul Eggleton
---
documentation/ref-manual/usingpoky.xml |8
1 file changed, 8 insertions(+)
diff --git a/documentation/ref-manual/usingpoky.xml
Buildhistory now collects information on SRCREV values for recipes
fetched from a version control system e.g. Git; additionally a
buildhistory-collect-srcrevs tool is provided to gather this and
convert it to a format suitable for inclusion in global configuration.
Add information on these new feat
Buildhistory can now collect information on SDK contents, so add this to
the appropriate section.
Signed-off-by: Paul Eggleton
---
documentation/ref-manual/usingpoky.xml | 62
1 file changed, 62 insertions(+)
diff --git a/documentation/ref-manual/usingpoky.xml
The following changes since commit 3b1c5858527cba908a5acff1ddc924630cc954b0:
dev-manual: merged "updating images" into the "working with packages"
(2013-04-03 09:12:49 -0700)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib paule/docs3
http://git.yoctoprojec
On Wednesday 03 April 2013 18:19:43 Hans Beckérus wrote:
> Hi. We wish to bring in the Erlang runtime into our builds, tailored for
> embedded systems.
> I can see that OpenEmbedded provides such a package in their classic
> release. But I can not seem to find it as part of Yocto, neither can I fin
Thanks Darren, will follow up on this.
Hi Paul,
Please try out what Darren has suggested.
-Kishore.
>-Original Message-
>From: Darren Hart [mailto:dvh...@linux.intel.com]
>Sent: Wednesday, April 03, 2013 8:39 AM
>To: Paul D. DeRocco
>Cc: yocto@yoctoproject.org; Bodke, Kishore K
>Subject
On 04/03/2013 12:19 PM, Hans Beckérus wrote:
> Hi. We wish to bring in the Erlang runtime into our builds, tailored for
> embedded systems.
> I can see that OpenEmbedded provides such a package in their classic
> release. But I can not seem to find it as part of Yocto, neither can I find
> it among
Hi. We wish to bring in the Erlang runtime into our builds, tailored for
embedded systems.
I can see that OpenEmbedded provides such a package in their classic
release. But I can not seem to find it as part of Yocto, neither can I find
it among the official OpenEmbedded recipes from their Wiki inde
"Paul D. DeRocco" writes:
> Followup:
>
> I figured I'd try a sato build, since that's what the example on the BSP
> page uses. But core-image-sato-cedartrail-nopvr panics in the same way as
> core-image-base-cedartrail-nopvr. For sato, I surmised maybe 1GB wasn't
> enough, so I put in a second s
Hi Paul,
First off, please CC the relevant maintainers of the recipes and BSPs
you are having trouble with. The README in the cedartrail BSP lists
Kishore as the maintainer, now on CC. This will help improve response
time to your post as well as getting the right people looking at it.
Kishore, ca
On 13-04-03 10:56 AM, Christophe Aeschlimann wrote:
Hi,
I'm using the danny branch and I would like to know if there is a way to
not have the zImage included in the generated image under the /boot/ folder.
I'm trying to save on space in the generated image and I couldn't find
anywhere to config
Hi,
On 3 April 2013 15:01, Edward Vidal wrote:
> What is the correct procedure to add bitbake results to the target?
http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-customimage-localconf
Generally you can specify the key packages and the dependencies will
pu
Hi,
I'm using the danny branch and I would like to know if there is a way to
not have the zImage included in the generated image under the /boot/ folder.
I'm trying to save on space in the generated image and I couldn't find
anywhere to configure that behaviour.
Thank you,
--
Christophe Aeschl
Hi Edward,
On Wednesday 03 April 2013 08:01:55 Edward Vidal wrote:
> I have been using the bitbake core-image-sato with
>
> EXTRA_IMAGE_FEATURES = "debug-tweaks tools-sdk" which adds the sdk to the
> image.
>
> I since have done bitbake boost (added about 14 RPMs) and bitbake
> qt-mobility-x11 (
Hello,
I have been using the bitbake core-image-sato with
EXTRA_IMAGE_FEATURES = "debug-tweaks tools-sdk" which adds the sdk to the
image.
I since have done bitbake boost (added about 14 RPMs) and bitbake
qt-mobility-x11 (81 RPMs).
After creating the boost libs I installed the 14 RPMs on the tar
2013/4/3 Michael Fainstein :
>> -Original Message-
>> From: Samuel Stirtzel [mailto:s.stirt...@googlemail.com]
>> Sent: יום ד 03 אפריל 2013 13:47
>> To: Paul Eggleton
>> Cc: Michael Fainstein; yocto@yoctoproject.org
>> Subject: Re: [yocto] how to convert source rpm spec to bitbake recipe?
>
> -Original Message-
> From: Samuel Stirtzel [mailto:s.stirt...@googlemail.com]
> Sent: יום ד 03 אפריל 2013 13:47
> To: Paul Eggleton
> Cc: Michael Fainstein; yocto@yoctoproject.org
> Subject: Re: [yocto] how to convert source rpm spec to bitbake recipe?
>
> 2013/4/3 Paul Eggleton :
> > Hi
2013/4/3 Paul Eggleton :
> Hi Michael,
>
> On Sunday 31 March 2013 08:45:23 Michael Fainstein wrote:
>> Is there a tool or guide for conversion of source rpm spec file to bitbake
>> recipe?
>
> There is scripts/create-recipe - this is aimed at just downloading source and
> using a spec file contain
Hi Eren,
On 28 March 2013 14:21, Eren Türkay wrote:
> I haven't prepared slides and I have one week until the event. I would
> really appreciate a previous seminar materials and slides. I would be
> grateful if we can discuss further on items in detail (e.g: what to
> explain). If you were to gi
On Wednesday 03 April 2013 08:42:23 Grigoropol, IoanaX wrote:
> Paul Eggleton wrote:
> > On Tuesday 12 March 2013 18:05:33 Ioana Grigoropol wrote:
> > > - support for clutter was removed from core-image-sato along with
> > > clutter-box2d and thus the project templates in Eclipse should not be
> >
Hi Guys,
I have a small issue. On my device, I would like to have Chinese, Japanese,
Russian, Hebrewish, Greek fonts and all European language special
characters available for java application based on X.
In general I would like to know a method of adding custom fonts which are
scalable to X serv
Hi Paul,
In my opinion, since clutter was only brought in core-image-sato and
core-image-sato-sdk by clutter-box2d, and not independently, it means it was
not really intended to support it.
Do you think there should be support for clutter in the sdk images ?
Clutter + dependencies is not a sma
Thanks for your reply..
It worked..
On Apr 3, 2013 12:58 PM, "Paul Eggleton"
wrote:
> On Friday 15 March 2013 14:12:45 Navani Srivastava wrote:
> > I tried giving
> > PREFERRED_PROVIDER_qt4_embedded ?= "4.8.1"
> >
> > in machine configuration file but it didn't helped..
> > Any suggestions?
>
> T
Hi Ioana,
On Tuesday 12 March 2013 18:05:33 Ioana Grigoropol wrote:
> - support for clutter was removed from core-image-sato along with
> clutter-box2d and thus the project templates in Eclipse should not be
> supported anymore; gtk templates should be used instead
The removal of clutter-box2d do
On Friday 15 March 2013 14:12:45 Navani Srivastava wrote:
> I tried giving
> PREFERRED_PROVIDER_qt4_embedded ?= "4.8.1"
>
> in machine configuration file but it didn't helped..
> Any suggestions?
This should be PREFERRED_VERSION_qt4-embedded = "4.8.1"
(note VERSION not PROVIDER, qt4-embedded not
I want to debug the kernel module loaded in the x86_64 (jasperforest)
linux-yocto target,
so I load the 'vmlinux' with gdb on the host PC (CentOS 6.4_x64) ,
but looks like the gdb failed to connect the target,
should I add any 'kernel boot parameters' to enable the kgdb use ttyS0 ?
my target boot
Hi Michael,
On Sunday 31 March 2013 08:45:23 Michael Fainstein wrote:
> Is there a tool or guide for conversion of source rpm spec file to bitbake
> recipe?
There is scripts/create-recipe - this is aimed at just downloading source and
using a spec file contained within as a basis for a new recip
On Apr 2, 2013, at 11:56 PM, Paul Eggleton
wrote:
> On Tuesday 02 April 2013 23:44:06 Khem Raj wrote:
>> On Apr 2, 2013, at 11:41 PM, Paul Eggleton
> wrote:
>>> I'm not sure this is a path we should be going down; potentially we could
>>> end up having to use ??= for just about everything.
>>
On Tuesday 02 April 2013 23:44:06 Khem Raj wrote:
> On Apr 2, 2013, at 11:41 PM, Paul Eggleton
wrote:
> > I'm not sure this is a path we should be going down; potentially we could
> > end up having to use ??= for just about everything.
>
> whats is downside of using ??= instead of ?=
The volume
On Apr 2, 2013, at 11:41 PM, Paul Eggleton
wrote:
> I'm not sure this is a path we should be going down; potentially we could end
> up having to use ??= for just about everything.
>
whats is downside of using ??= instead of ?=
> Wouldn't you be better off using your own separate distro conf
On Tuesday 02 April 2013 22:11:50 Khem Raj wrote:
> This is to facilitate distros using poky as reference
> so that they can use ?= and provide an option for their
> users to override it if desired
>
> Signed-off-by: Khem Raj
> ---
> meta-yocto/conf/distro/poky.conf |2 +-
> 1 file changed,
48 matches
Mail list logo
