All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: Andrei Gherzan <andrei@gherzan.ro>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: [meta-raspberrypi][PATCH 1/1] gstreamer1.0-plugins-bad: Build eglglessink for Raspberry Pi
Date: Wed, 11 Jun 2014 08:28:48 +0100	[thread overview]
Message-ID: <53980530.8000705@dynamicdevices.co.uk> (raw)
In-Reply-To: <53979352.6040909@dynamicdevices.co.uk>

[-- Attachment #1: Type: text/plain, Size: 2854 bytes --]


On 11/06/2014 00:22, Alex J Lennon wrote:
>
> On 10/06/2014 19:48, Andrei Gherzan wrote:
>> Hi Alex,
>>
>>
>> On Mon, Jun 9, 2014 at 10:23 AM, Alex J Lennon
>> <ajlennon@dynamicdevices.co.uk
>> <mailto:ajlennon@dynamicdevices.co.uk>> wrote:
>>
>>     The eglglessink needs to be built to target the Raspberry Pi or
>>     it will seg-fault in use.
>>
>>     Autoconf attempts to detect whether to build for RPi but there
>>     are some include files needed, the search path to which must be
>>     specified.
>>
>>
>> Format lines - max 78 chars per line.
>>  
>>
>>
>>     ref: https://github.com/raspberrypi/firmware/issues/34
>>
>>     ref: https://github.com/raspberrypi/firmware/issues/99
>>
>>     This patch adds the needed include paths and forces the plugin to
>>     be built for Raspberry Pi.
>>
>>     With this patch the following pipeline works on RPi,
>>
>>     modprobe bcm2835-v4l2 gst_v4l2src_is_broken=1
>>     gst-launch-1.0 --gst-debug-no-color v4l2src !
>>     'video/x-raw,format=RGB,width=1280,height=720,framerate=(fraction)30/1'
>>     ! eglglessink max-lateness=-1
>>
>>     Change-Id: I80826a43a428199b2a05ea51404ead24a815c38f
>>     Signed-off-by: Alex J Lennon <ajlennon@dynamicdevices.co.uk
>>     <mailto:ajlennon@dynamicdevices.co.uk>>
>>     ---
>>      recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.2.3.bbappend
>>     | 1 +
>>      1 file changed, 1 insertion(+)
>>      create mode 100644
>>     recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.2.3.bbappend
>>
>>     diff --git
>>     a/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.2.3.bbappend
>>     b/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.2.3.bbappend
>>     new file mode 100644
>>     index 0000000..199e0c1
>>     --- /dev/null
>>     +++
>>     b/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.2.3.bbappend
>>     @@ -0,0 +1 @@
>>     +EXTRA_OECONF += "
>>     CPPFLAGS='-I${STAGING_DIR_TARGET}/usr/include/interface/vcos/pthreads
>>     -I${STAGING_DIR_TARGET}/usr/include/interface/vmcs_host/linux'
>>     --with-egl-window-system=rpi"
>>
>>
>> This append should be done only for raspberrypi machine. Having this
>> append (EXTRA_OECONF) for other machines too would
>> break gstreamer1.0-plugins-bad as most of the times bblayers.conf
>> includes many layers not always related to the MACHINE selected.
>
> Absolutely. Our emails may have crossed here and if so my apologies,
> but this is why I directed the .bbappend to [meta-raspberrypi] as
> that's where it's needed.

Andrei - Upon further reflection I see what you mean. Somebody might
well include the meta-raspberrypi layer, yet not be building for the
Raspberry Pi. Not something I'd considered. I'll re-work the patch to
take this into account.

Cheers, Alex


[-- Attachment #2: Type: text/html, Size: 5751 bytes --]

  reply	other threads:[~2014-06-11  7:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09  6:58 [meta-raspberrypi][PATCH 0/1] gstreamer1.0-plugins-bad: Build eglglessink for Raspberry Pi Alex J Lennon
2014-06-09  6:58 ` [meta-raspberrypi][PATCH 1/1] " Alex J Lennon
2014-06-10 18:48   ` Andrei Gherzan
2014-06-10 23:22     ` Alex J Lennon
2014-06-11  7:28       ` Alex J Lennon [this message]
2014-06-11  7:33         ` Andrei Gherzan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53980530.8000705@dynamicdevices.co.uk \
    --to=ajlennon@dynamicdevices.co.uk \
    --cc=andrei@gherzan.ro \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.