Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 0/4] Add GStreamer 0.10 and things that depend on it from oe-core
Date: Thu, 21 May 2015 16:11:44 +0200	[thread overview]
Message-ID: <20150521141144.GG2377@jama> (raw)
In-Reply-To: <555DE57B.1050706@linux.intel.com>

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

On Thu, May 21, 2015 at 05:02:35PM +0300, Alexander Kanavin wrote:
> On 05/21/2015 04:48 PM, Martin Jansa wrote:
> > No you don't need to copy it, just use path to it, I've already fixed 
> > it for my jenkins builds, you don't need to resend just because of this..
> 
> I wanted to send an updated set, because also this recipe requires a 
> file with a path, so that will break after the directory rename (to 
> gstreamer-0.10) patch is applied:

Are you going to rename gstreamer to gstreamer-0.10 in oe-core? I don't
think so or I misunderstood what you meant, these 2 lines look correct
to me:
$ git grep gst-plugins-package.inc
meta-multimedia/recipes-multimedia/gstreamer/gst-plugins.inc:require recipes-multimedia/gstreamer/gst-plugins-package.inc
meta-oe/recipes-connectivity/bluez/gst-plugin-bluetooth_4.101.bb:require recipes-multimedia/gstreamer/gst-plugins-package.inc

and renaming the directory in meta-multimedia doesn't have any impact on
this.

> gst-plugins-gl_0.10.3.bb:require 
> recipes-multimedia/gstreamer/gst-plugins.inc
> 
> 
> Here the path should be removed instead.
> 
> 
> Alex
> -- 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2015-05-21 14:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18 14:12 [PATCH 0/4] Add GStreamer 0.10 and things that depend on it from oe-core Alexander Kanavin
2015-05-18 14:12 ` [PATCH 1/4] python-gst: move it from oe-core to meta-multimedia Alexander Kanavin
2015-05-18 14:12 ` [PATCH 2/4] recipes-qt: move qt-mobility from oe-core to meta-oe Alexander Kanavin
2015-05-18 14:12 ` [PATCH 3/4] recipes-multimedia: add gstreamer-0.10 recipes Alexander Kanavin
2015-05-18 14:12 ` [PATCH 4/4] Rename gstreamer directory to gstreamer-0.10 Alexander Kanavin
2015-05-18 14:16   ` Carlos Rafael Giani
2015-05-18 14:24     ` Alexander Kanavin
2015-05-18 16:58     ` Burton, Ross
2015-05-21 11:06 ` [PATCH 0/4] Add GStreamer 0.10 and things that depend on it from oe-core Martin Jansa
2015-05-21 13:33   ` Alexander Kanavin
2015-05-21 13:48     ` Martin Jansa
2015-05-21 14:02       ` Alexander Kanavin
2015-05-21 14:11         ` Martin Jansa [this message]
2015-05-21 14:19           ` Alexander Kanavin
2015-05-22 16:11   ` akuster808
2015-05-22 16:30     ` Burton, Ross
2015-05-25 16:39       ` akuster808
2015-05-26  9:01         ` Burton, Ross
2015-05-26 12:26         ` Alexander Kanavin
2015-06-05  8:40       ` Huang, Jie (Jackie)

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=20150521141144.GG2377@jama \
    --to=martin.jansa@gmail.com \
    --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