On 9 April 2014 00:03, Patrick Doyle wrote:
> I have a ridiculously pinhole sized memory footprint into which I
> would like to squeeze a gstreamer based video pipeline. I am looking
> for tips on what I can do to minimize the footprint as much as
> possible for my Yocto based system.
The GStrea
Thank you, Erik.
Best Regards,
Zhenhua
> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-
> boun...@yoctoproject.org] On Behalf Of Erik Bot?
> Sent: Wednesday, April 09, 2014 2:47 PM
> To: Luo Zhenhua-B19537
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Ca
Hi all,
I am looking into collecting feedback on the first version of Toaster
https://www.yoctoproject.org/blogs/belenbarrospena/2014/eye-candy
which will be out with Yocto Project 1.6. There are 2 things I'd like to
do:
1) Dogfooding
Once the release is out, it would be great to have people t
Hi Vali,
On Tuesday 08 April 2014 18:34:08 Vali Cobelea wrote:
> Here at ENEA we decided to take the initiative regarding the CGL
> compliance when it comes to the Yocto Project.
> For this we started the work on a dedicated layer called 'meta-cgl'
> which can be accessed / cloned from here:
>
>
Hi,
Thank you for the input.
We will keep the layer for a short period of time at the current
location while getting other ideas regarding the content / architecture.
The layer initiative will also be raised up in the board advisory
meeting, in order to get even more input.
After which we will
On Wednesday 09 April 2014 13:55:47 Vali Cobelea wrote:
> On 04/09/2014 01:51 PM, Paul Eggleton wrote:
> > On Tuesday 08 April 2014 18:34:08 Vali Cobelea wrote:
> >> Here at ENEA we decided to take the initiative regarding the CGL
> >> compliance when it comes to the Yocto Project.
> >> For this we
Thank you for the tips folks... please keep them coming. At the moment
(for this pinhole sized project) I only need support for video. Is
there any way to strip out all of the audio components from the
gstreamer I generate? I tried adding --disable-vorbis to my recipe,
only to find that config.s
OK Paul, that indeed makes sense, I really did not knew that preliminary
versions of layers are accepted.
I will discuss around here and if everything goes OK we will start the
move in the "public" layer index.
I also do agree with an all-together strategy, no matter for the layer
state.
Much
It seems people don't understand what the point of a Release Candidate
is, or the timelines we work to. The fact this is coming as a surprise
to people is seriously upsetting to me as we've done this for long
enough now that people should know the drill.
A release candidate is what is says, a poss
We are working on a project where we will be receiving different types of
artifacts from various development groups within the organization.
Specifically, we will receive kernel images (qemux86, qemuarm, and ATOM) as
well as RPMs. We'd like to incorporate those artifacts directly into our
proje
Hello everyone,
In comparision to ${S}, the variable ${D} isn't documented very well in the
ref-manual. I wanted to improve on that a little bit.
Please review the attached patch (on correctness of the statements especially).
It would be cool to see this mainline soon.
With best regards,
Dennis
Dennis,
Thanks for the patch. I have applied it for the upcoming 1.6 release. You can
examine it at
http://www.yoctoproject.org/docs/1.6/ref-manual/ref-manual.html#var-D. When
applying your patch, I performed some minor style editing to conform to some
standards within the YP documentation
Hi,
Disabling the GStreamer debugging system can also help trim off a
decent amount from the packages.
Edward
On Wed, 2014-04-09 at 07:13 -0400, Patrick Doyle wrote:
> Thank you for the tips folks... please keep them coming. At the moment
> (for this pinhole sized project) I only need sup
I am getting the following warning:
WARNING: Setscene task 45
(/home/jate/workspace/poky/meta/recipes-connectivity/avahi/avahi-ui_0.6.31.bb,
do_populate_sysroot_setscene) failed with exit code '1' - real task
will be run instead
The task log.do_populate_sysroot_setscene has the following WARNING:
On 04/09/2014 03:43 AM, Barros Pena, Belen wrote:
> Hi all,
>
> I am looking into collecting feedback on the first version of Toaster
>
> https://www.yoctoproject.org/blogs/belenbarrospena/2014/eye-candy
>
> which will be out with Yocto Project 1.6. There are 2 things I'd like to
> do:
>
> 1) D
On Wed, Apr 9, 2014 at 1:52 PM, Jate S wrote:
> WARNING: Setscene task 45
> (/home/jate/workspace/poky/meta/recipes-connectivity/avahi/
> avahi-ui_0.6.31.bb,
> do_populate_sysroot_setscene) failed with exit code '1' - real task
> will be run instead
>
> The task log.do_populate_sysroot_setscene h
Hi Belen,
That is exciting. I just ran with it and started a build with toaster in
the background. A couple of observations from the get-go:
- South 0.8.4 is also needed in addition to Django. The Toaster Wiki [1]
does not say that but the Contribute to Toaster page [2] does.
- You need
On Wed, Apr 9, 2014 at 4:33 PM, Rudolf Streif wrote:
> That is exciting. I just ran with it and started a build with toaster in
> the background. A couple of observations from the get-go:
>
>- South 0.8.4 is also needed in addition to Django. The Toaster Wiki
>[1] does not say that but the
All,
We have an rc3 build for our upcoming 1.6 release. We had to rebuild
the eclipse-poky-kepler
plugin due to some incompatibility with the debian 7 builder. We also
have issues in
nightly-oecore:
http://autobuilder.yoctoproject.org/main/builders/nightly-oecore/builds/39
and
http://autobuilder.
19 matches
Mail list logo