[meta-freescale] Regarding GStreamer-1.x status on iMX6Q
joshua.kurland at adtecdigital.net
Mon Dec 9 13:26:05 PST 2013
Ah, okay. Gst-inspect-1.0 now shows imxvpu, imxipu, etc. In order to
decode a simple video from a file, what would the new pipeline look like?
Normally I would run something like 'gst-launch-0.10 playbin2
uri=file:///myfile video-sink=mfw_v4lsink'. Can I make a one-to-one
conversion from the old mfw_v4lsink to some other custom element?
On Mon, Dec 9, 2013 at 4:17 PM, Carlos Rafael Giani
<dv at pseudoterminal.org>wrote:
> Thats because they have different names. They all start with "imx" (with
> the exception of the eglvivsink).
> These are entirely different plugins, written from scratch.
> On 2013-12-09 22:14, Joshua Kurland wrote:
> Thanks Carlos, that script helped out a lot and I am able to compile the
> binaries. I modified your script to use the wandboard-quad sysroots and
> ran the script. I then ran ./waf and sudo ./waf install. I copied the
> binaries from /usr/local/lib to my board in /usr/lib and
> /usr/lib/gstreamer-1.0. Everything seemed fine, but when I use
> gst-inspect-1.0 to find mfw_v4lsink nothing is found. The same can be said
> for other Freescale elements that I had been using in Gstreamer-0.10.
> Josh Kurland
> On Mon, Dec 9, 2013 at 3:31 PM, Carlos Rafael Giani <dv at pseudoterminal.org
> > wrote:
>> On 2013-12-09 21:05, Joshua Kurland wrote:
>>> I am having a bit of difficulty compiling the gstreamer-imx binaries
>>> using waf. I set up the environment variables and ran waf, but it was
>>> unable to find 'libfslvpuwrap'. But libfslvpuwrap.pc is found in my
>>> I am adding libfslvpuwrap as a package under the IMAGE_INSTALL section of
>>> my image recipe, is this not the correct way? I've attached my environment
>>> script as well as the error log, I would appreciate any help I can get.
>>> Josh Kurland
>> The environment variables look wrong to me.
>> 1. export
>> : sysroot is not supposed to point to the cross compiler directory, but to
>> the sysroot of the *device* (same goes for the LDFLAGS, the
>> PKG_CONFIG_SYSROOT_DIR, and the kernel headers path)
>> 2. the "/build" part of the kernel headers path needs to be removed
>> 3. do you use hardfloat or softfloat? In one place, you use cortexa9, in
>> another, cortexa9hf
>> I attached an example script that may be clearer (at successfully builds
>> the plugins). It builds for the Sabre SD DualLite platform.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the meta-freescale