[yocto] Empty "normal" package, filled dev and dbg packages, tr-50 lib

[Paul Eggleton]

Hi Jakob,

On Tuesday, 31 January 2017 5:53:47 PM NZDT Jakob Hasse wrote:
> I still try to include the tr-50 library into my build, which is an
> autotools manages library. The code is fetch from git by bitbake.
> The good thing: it builds, the compilation of the library itself gives
> no errors and after it I find the .so files several times in the build
> directory.
> However, the packaging does not work as intended:
> It builds the dev and dbg Versions of the package, but not the "normal"
> version of the package:
> ls
> ./tmp/work/armv7a-vfp-neon-dey-linux-gnueabi/tr-50/0.1-r0/deploy-rpms/armv7a
> _vfp_neon/ tr-50-dbg-0.1-r0.armv7a_vfp_neon.rpm
> tr-50-dev-0.1-r0.armv7a_vfp_neon.rpm

It's very likely that do_install isn't installing files into the right place, 
or isn't installing anything with the result that nothing but -dev and -dbg 
packages are created (they are marked ALLOW_EMPTY by default so they will 
always be written out).
 
> I could make bitbake building that package but that package was empty then.
> 
> My recipe:
> 
> DESCRIPTION = "the tr-50 (MQTT) library to communicate with the swisscom
> devicewise cloud"
> SECTION = "libs"
> LICENSE = "Unknown"
> LIC_FILES_CHKSUM = "file://COPYING;md5=c8ee358fdf91d887aa014c8712e8c22d"
> # md5sum only when source is a tar.gz
> SRC_URI[md5sum] = "da7315f9bc22ff4c24a1cef404b4f3a8"
> SRC_URI = "git://github.com/inhedron/libtr50.git;protocol=https"
> SRCREV = "aedc45c4e9a9a9a3aa301616ad03f07b903d9a81"
> 
> # tryed the three lines below already, didn't help:
> #FILES_${PN}-dev = ""
> #FILES_SOLIBSDEV = ""
> #ALLOW_EMPTY_${PN} = "1"

Right, none of that is going to help.
 
What you really need to do is look in the install destination directory - i.e. 
the "image" subdirectory under the work directory - you can find the latter 
pretty easily if you're unsure:

bitbake -e tr-50 | grep ^WORKDIR=

Where are files being installed under there? Are there any files there at all?
Once we see what's there we can figure out what the fix will be.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre