[yocto] Files missing from SDK

[Paul Eggleton]

On Tuesday, 7 March 2017 2:28:22 AM NZDT Gary Thomas wrote:
> On 2017-03-06 13:22, Burton, Ross wrote:
> > On 3 March 2017 at 06:39, Gary Thomas <gary at mlbassoc.com 
<mailto:gary at mlbassoc.com>> wrote:
> >     I'm trying to build SDKs for my board, both the native style
> >     using populate_sdk_ext as well as including the SDK packages
> >     in my image.  My image includes some extended libraries of
> >     my own packaging (am335x-pru-support) that I need to get into
> >     these SDKs.  This package (via debian renaming) turns into
> >     
> >       libprussdrv-dbg - 2016-08-30-r0.23 - am335x-pru-support version
> >       2016-08-30-r0 - Debugging files libprussdrv-dev - 2016-08-30-r0.23
> >       - am335x-pru-support version 2016-08-30-r0 - Development files
> >       libprussdrv-staticdev - 2016-08-30-r0.23 - am335x-pru-support
> >       version 2016-08-30-r0 - Development files (St) libprussdrv1 -
> >       2016-08-30-r0.23 - am335x-pru-support version 2016-08-30-r0>     
> >     On my board/image, I can get the files I need but only if I manually
> >     include libprussdrv-dev>     
> >       # opkg files libprussdrv-dev | sort
> >       /usr/bin/pasm
> >       /usr/include/pruss/
> >       /usr/include/pruss/pruss_intc_mapping.h
> >       /usr/include/pruss/prussdrv.h
> >       /usr/lib/libprussdrv.so
> >     
> >     How can I get these automatically added to my SDK images?  To build
> >     the
> >     
> >     board SDK, I'm adding these packages to my image:
> >       CORE_IMAGE_EXTRA_INSTALL = "packagegroup-core-sdk
> >       packagegroup-core-standalone-sdk-target">     
> >     I suppose I could add libprussdrv-dev to that list, but I'd like it a
> >     bit more automated.>     
> >     For the native SDK, I tried adding this to local.conf:
> >       TOOLCHAIN_HOST_TASK_append = " nativesdk-am335x-pru-support"
> >     
> >     which only got me the 'pasm' tool in my sysroot, but nothing else.
> > 
> > If libprussdrv1 is in your image then the -dev package should be pulled
> > into your SDK images, assuming that you have IMAGE_FEATURES+=dev-pkgs
> > already.
> 
> Thanks, that did it for the embedded SDK

That shouldn't actually be necessary. IMAGE_FEATURES controls what goes into 
the image, adding dev-pkgs to that is going to include those in the image, not 
just the SDK. We have a SDKIMAGE_FEATURES and the default value of that 
includes dev-pkgs. If libprussdrv1 is in the image and SDKIMAGE_FEATURES is at 
the default (or otherwise includes dev-pkgs) I have to say I'm not sure what 
would be preventing this from working.

> > The same should mean that standalone SDKs (populate_sdk-style) contain the
> > headers too.  Worse case, TOOLCHAIN_TARGET_TASK_append = "
> > libprussdrvi-dev".
> 
> Sadly, this still doesn't work.  With the TOOLCHAIN* line above, I get:
>    ERROR: Nothing RPROVIDES 'libprussdrv1-dev'
> Without it, no changes - the bits are still missing.

As with almost all variables, in TOOLCHAIN_TARGET_TASK you want the recipe-
space name of the package, not the final (post debian-renamed) name.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre