[OE-core] yajl: Installed (but unpackaged) file(s) found

[Stuart Yoder]

yajl/libyajl is a dependeny I have for another package I'm trying to
build so I'm not touching the yajl recipe at all.  In fact the
complete recipe is this:

---------------------------------
DESCRIPTION = "Yet Another JSON Library - A Portable JSON parsing and serializat
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://COPYING;md5=74f541bd9a2b6c8e5d0714bcdc327f32"

SRCREV = "fee1ebef9fa7dc0e9f5a23f37123b19b68c796ff"
SRC_URI = "git://github.com/lloyd/yajl.git"

S = "${WORKDIR}/git"

inherit cmake lib_package
---------------------------------

It's just my observation that there seems to be a discrepancy between
what is getting built and packaged.   Things get built in ./lib and
packaged from ./lib64.

Do I really need to explicitly define FILES_yajl in this recipe?   It
seems like yajl is not the only package that might have this kind of
issue.   I have this feeling that there might be some simpler fix, but
I'm a novice at Yocto.

Stuart

On Thu, May 2, 2013 at 4:36 AM, Paul Eggleton
<paul.eggleton at linux.intel.com> wrote:
> On Thursday 02 May 2013 10:24:10 Burton, Ross wrote:
>> On 1 May 2013 20:11, Stuart Yoder <b08248 at gmail.com> wrote:
>> >    FILES_yajl="/usr/bin/* /usr/sbin/* /usr/lib64/yajl/* ...
>> >
>> > Ho do I get the yajl recipe to either a) build the files in lib64 or
>> > b) package them from lib.
>>
>> Don't hard-code paths, instead use the symbols available in bitbake.conf:
>>
>> FILES_yajl = "${bindir}/* ${sbindir}/* ${libdir}/yajl/*"
>
> You should also use FILES_${PN} rather than FILES_yajl.
>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre