All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: Joshua Kurland <joshua.kurland@adtecdigital.net>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: Regarding GStreamer-1.x status on iMX6Q
Date: Mon, 09 Dec 2013 22:17:53 +0100	[thread overview]
Message-ID: <52A63381.7000609@pseudoterminal.org> (raw)
In-Reply-To: <CAPuotkcMo=BBhp=9gs_d7=KVBF=9iGjFEbL3ZCtDTC1g3YA4Vg@mail.gmail.com>

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

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.
>
> Thanks,
> Josh Kurland
>
>
> On Mon, Dec 9, 2013 at 3:31 PM, Carlos Rafael Giani 
> <dv@pseudoterminal.org <mailto:dv@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
>         sysroot/cortexa9hf-vfp-neon-poky-linux-gnueabi/usr/lib/pkgconfig/libfslvpuwrap.pc.
>          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.
>
>         Thanks,
>         Josh Kurland
>
>
>     The environment variables look wrong to me.
>     1. export
>     CFLAGS="--sysroot=/opt/poky/1.5+gst/sysroots/x86_64-linux/usr/bin/cortexa9-vfp-neon-poky-linux-gnueabi"
>     : 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.
>
>     cheers
>
>


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

  reply	other threads:[~2013-12-09 21:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18 15:48 Regarding GStreamer-1.x status on iMX6Q Joshua Kurland
2013-11-18 16:07 ` Otavio Salvador
2013-11-18 16:54   ` Carlos Rafael Giani
2013-11-18 18:20     ` Joshua Kurland
2013-11-20 13:24       ` Carlos Rafael Giani
2013-11-20 15:25         ` Joshua Kurland
2013-11-20 18:52           ` Carlos Rafael Giani
2013-11-21  1:59           ` Philip Craig
2013-12-02  1:36       ` Carlos Rafael Giani
2013-12-09 20:05         ` Joshua Kurland
2013-12-09 20:31           ` Carlos Rafael Giani
2013-12-09 21:14             ` Joshua Kurland
2013-12-09 21:17               ` Carlos Rafael Giani [this message]
2013-12-09 21:26                 ` Joshua Kurland
2013-12-09 21:31                   ` Carlos Rafael Giani
2013-12-10 18:52                     ` Joshua Kurland
2013-12-10 19:01                       ` Carlos Rafael Giani
2013-12-10 19:15                         ` Joshua Kurland

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=52A63381.7000609@pseudoterminal.org \
    --to=dv@pseudoterminal.org \
    --cc=joshua.kurland@adtecdigital.net \
    --cc=meta-freescale@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.