Hello Bharath,

This is already known to me. The confusion mainly here was because of the name of the rpm package. From the recipe expected name was "nativesdk-qtbase-tools-dev-5.2.1-r1.i686_nativesdk.rpm" but generated package name is "nativesdk-libqt5core-dev-5.2.1-r1.i686_nativesdk.rpm" which confused me.

As Mr. Burton mentioned in his last mail, this was done by "debian.bbclass", which makes our life more difficult. So I feel a tool to track this relations is really necessary, and I guess yocto has done this in Yocto 1.6 with "toaster" (I still have to use it and see).

Regards,
Anooj


On Tue, Jul 22, 2014 at 6:37 PM, Bharath Chandra <ellurubharath29@gmail.com> wrote:
Hi,

you can find it under .inc file here
https://github.com/meta-qt5/meta-qt5/blob/daisy/recipes-qt/qt5/nativesdk-qtbase.inc
PACKAGES = "${PN}-tools-dbg ${PN}-tools-dev ${PN}-tools-staticdev ${PN}-tools"

Thanks,
Bharath


On Tue, Jul 22, 2014 at 11:19 AM, Anooj Gopi <anoojgopi@gmail.com> wrote:
Manually searching the bb/inc file did not help until this point.

Now I enabled the build history (INHERIT += "buildhistory" BUILDHISTORY_FEATURES = "image package sdk") and built the packages once again. Then searched for the package name as shown below

cd build/buildhistory/packages
grep -nri nativesdk-libqt5core-dev .
./i686-nativesdk-oesdk-linux/nativesdk-qtbase/nativesdk-qtbase-tools-dev/latest:3:PKG = nativesdk-libqt5core-dev

which shows that the yocto package is "nativesdk-qtbase-tools-dev", which is provided by "nativesdk-qtbase_5.2.1.bb".

But I'm still not able to find out where in yocto PKG variable is configured (which changes this rpm file name from the default one).



On Tue, Jul 22, 2014 at 5:50 PM, Bharath Chandra <ellurubharath29@gmail.com> wrote:
Hi Anooj,

I guess you are looking at a wrong version of the recipe file, you have to look into version number 5.2.1 and revision r1 as your package name is suggesting but the link which you have mentioned is for 5.3.1 . Kindly, have a look into correct version number of recipe file and if you do not find any package name in the recipe file then you can search in .inc files which are included in that recipe file.
for eg : 
require qt5-${PV}.inc





You have to check in qt5-5.2.1.inc file and see if any package is included with the name which you are searching for.





Thanks & Regards,
Bharath Chandra Elluru


On Tue, Jul 22, 2014 at 6:52 AM, Anooj Gopi <anoojgopi@gmail.com> wrote:

Yes I am trying to track down the recipe from the rpm file. In my project yocto builds the rpm package "nativesdk-libqt5core-dev-5.2.1-r1.i686_nativesdk.rpm" (by https://github.com/meta-qt5/meta-qt5) but it is not included in my sdk sysroot image. So I would like to see how I could include this into my sdk. For that I am tracing back the recipe which generated the rpm.

I tried as you said:
From the source package name I can see it is from "Source RPM  : nativesdk-qtbase-5.2.1-r1.src.rpm", which means bb file is https://github.com/meta-qt5/meta-qt5/blob/master/recipes-qt/qt5/nativesdk-qtbase_5.3.1.bb
Now this from the bb file content I can see this file provides multiple packages, (for eg. nativesdk-qtbase-tools-dbg nativesdk-qtbase-tools-dev nativesdk-qtbase-tools-staticdev nativesdk-qtbase-tool) but I still could not find where it is configured to generate the package "nativesdk-libqt5core-dev-5.2.1-r1.i686_nativesdk.rpm".

As Belen in his last mail, the tools like "Toaster" could confirm this (by listing the packages generated from a bb file), but is there any way I can do it in Yocto Project 1.5?

Regards,
Anooj


On Tue, Jul 22, 2014 at 11:15 AM, Burton, Ross <ross.burton@intel.com> wrote:
On 21 July 2014 16:39, Anooj Gopi <anoojgopi@gmail.com> wrote:
> Could some one help me to understand how we could find the bb file which
> generated particular package (rpm package for eg.)?
> (In some cases the name of the package and recipe name differ drastically)
>
> Also is there any way to list packages (rpm) generated by particular recipe
> (yocto package) easily. (without looking into the PACKAGES variable).

It's probably best if you explain exactly what you want to do.

If you want to work backwards from a RPM to the recipe, then binary
RPMs have a Source RPM metadata field and the srpm is named after the
recipe:

$ rpm -qpi connman-tests-1.24-r0.15.corei7_64.rpm | grep Source
Source RPM  : connman-1.24-r0.15.src.rpm

Ross



--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto




--
Thanks & Regards,
Bharath Chandra Elluru.
Contact Number:785-979-4875.




--
Thanks & Regards,
Bharath Chandra Elluru.
Contact Number:785-979-4875.