gst-plugin-base libs not going to rootfs

gst-plugin-base libs not going to rootfs

[Yogesh Tyagi]

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

Hi,

I am using yocto 1.5 in my project. The problem is, gst-plugin-base
libraries are not going to rootfs in my build.

I have tried to write a bbappend file "gst-plugins-base_0.10.36.bbappend"
with below content:

S = "${WORKDIR}"

FILES_${PN} += " ${libdir}/gstreamer-0.10/*.so"
FILES_${PN}-dev += " ${libdir}/gstreamer-0.10/*.la
${libdir}/gstreamer-0.10/*.a"
FILES_${PN}-dbg += " ${libdir}/gstreamer-0.10/.debug/
${libexecdir}/gstreamer-0.10/.debug/"


do_install_append () {
         install -m 0755 ${S}/package/usr/lib/gstreamer-0.10/*
${D}${libdir}/gstreamer-0.10/
}

and I have also added "gst-plugin-base" to packagegroup bb file of my
project but still gst-plugins-base libs are not going to rootfs. Please
help.


Thanks,
Yogesh

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

Re: gst-plugin-base libs not going to rootfs

[Burton, Ross]

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

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

> and I have also added "gst-plugin-base" to packagegroup bb file of my
> project but still gst-plugins-base libs are not going to rootfs. Please
> help.
>

gst-plugins-base is an empty package.  If you want all plugins. install
gst-plugins-base-meta.

Ross

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

Re: gst-plugin-base libs not going to rootfs

[Yogesh Tyagi]

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

Hi Ross,

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.

Thanks,
Yogesh

-----Original Message-----
From: "Burton, Ross" <ross.burton@intel.com>
Sent: ‎26/‎05/‎2015 07:52 PM
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 14:10, Yogesh Tyagi <yogesh.bit2006@gmail.com> wrote:

and I have also added "gst-plugin-base" to packagegroup bb file of my project but still gst-plugins-base libs are not going to rootfs. Please help.

gst-plugins-base is an empty package.  If you want all plugins. install gst-plugins-base-meta.


Ross

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

Re: gst-plugin-base libs not going to rootfs

[Burton, Ross]

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

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: 968 bytes --]

Re: gst-plugin-base libs not going to rootfs

[Yogesh Tyagi]

[-- 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 --]