Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Ali Botorabi" <g.development@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: Problem with baking GStreamer Plugins
Date: Wed, 11 Feb 2009 11:51:04 +0100	[thread overview]
Message-ID: <20090211105104.67620@gmx.net> (raw)
In-Reply-To: <mailman.0.1234264323.11785.openembedded-devel@lists.openembedded.org>

Hello,

I am trying to include some of the GStreamer plugins into an own image. The image bases on angstrom base and X11 images. Koen helped me to setup a task for the GStreamer plugins:

-------------------------------------
DESCRIPTION = "ToDo"
LICENSE = "ToDo"
PR = "r1.4"

#PREFERRED_PROVIDER_gst-plugin-alsa ?= "gst-plugins-good"

DEPENDS = "gst-plugins-base gst-plugins-bad gst-plugins-good gst-plugins-ugly libogg libvorbis directfb"
RDEPENDS_${PN} = "\
        libid3tag \
        libsidplay \
        libvorbis \
        libogg \
        directfb \
        alsa-lib \
        gstreamer \
        gst-plugin-alsa \
        gst-plugin-icydemux \
        gst-plugin-asfdemux \
        gst-plugin-dvdlpcmdec \
        gst-plugin-mpegstream \
        gst-plugin-realmedia \
"

inherit task
------------------------------

This task is included by the image recipe. Bitbake evaluates the task and complains about various packages providing the plugins (base, good, ugly, bad). I have also tried to use PREFERRED_PROVIDER, it had no effect.

The major problem is that the plugins do not end in the image.

Any help is highly appreciated.

Cheers
Botorabi

-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01



       reply	other threads:[~2009-02-11 10:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.0.1234264323.11785.openembedded-devel@lists.openembedded.org>
2009-02-11 10:51 ` Ali Botorabi [this message]
2009-02-11 11:47   ` Problem with baking GStreamer Plugins Koen Kooi
2009-02-17 15:27 Ali Botorabi

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=20090211105104.67620@gmx.net \
    --to=g.development@gmx.net \
    --cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox