All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yogesh Tyagi <yogesh.bit2006@gmail.com>
To: bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: gst-plugin-base libs not going to rootfs
Date: Wed, 27 May 2015 22:20:34 +0530	[thread overview]
Message-ID: <5565f5dc.657e460a.7302.045f@mx.google.com> (raw)
In-Reply-To: <CAJTo0LbQk5EeDTPZ3m_WVYvJQy-jE8DviM1_zcc_94axGnZNfA@mail.gmail.com>

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

Hi,

I have verified that rpm packages generated by gst-plugins-base are not empty. Adding gst-plugins-base-meta doesn't help.

Thanks,
Yogesh


-----Original Message-----
From: "Burton, Ross" <ross.burton@intel.com>
Sent: ‎27/‎05/‎2015 02:54 AM
To: "Yogesh Tyagi" <yogesh.bit2006@gmail.com>
Cc: "bitbake-devel" <bitbake-devel@lists.openembedded.org>
Subject: Re: [bitbake-devel] gst-plugin-base libs not going to rootfs



On 26 May 2015 at 16:40, Yogesh Tyagi <yogesh.bit2006@gmail.com> wrote:

Thanks for replying. I have checked that when gst-plugins-base is build, it contains complete source and all the libraries are also getting created. How come this is an empty package?        
How do I know it's an empty package? I am a novice in bitbake/yocto.

The *recipe* builds correctly, but that recipe generates many packages.  You can see what packages have been created by looking in tmp/deploy, and use rpm/dpkg to inspect the contents.


Ross

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

      reply	other threads:[~2015-05-27 16:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-26 13:10 gst-plugin-base libs not going to rootfs Yogesh Tyagi
2015-05-26 14:22 ` Burton, Ross
2015-05-26 15:40   ` Yogesh Tyagi
2015-05-26 21:24     ` Burton, Ross
2015-05-27 16:50       ` Yogesh Tyagi [this message]

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=5565f5dc.657e460a.7302.045f@mx.google.com \
    --to=yogesh.bit2006@gmail.com \
    --cc=bitbake-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 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.