[yocto] Using files from package dependencies

[Paulo Neves]

Hello Nicolas, thank you for your advice and hints but I "need" to
corrupt a bit the conventions of yocto and use specific package names
(due to compatibility with other older build systems)

The magic behind the fact that my special package sysroot directories
were not being moved to the yocto sysroot was due to the fact that
do_populate_sysroot does not match all the toplevel directories in
${D}. For additional directories sysroot_stage_all needs to be
appended with the desired directories. I am perfectly ok with that but
why not make a notification that there were directories that were
packaged but will not be expanded in the sysroots? The lack of
notification is extremely confusing, as files just do not appear where
they should.

A similar question to mine can be found here:
http://stackoverflow.com/questions/35354802/how-to-create-do-populate-sysroot-append-task-in-yocto/40976056#40976056

Best regards
Paulo Neves

On Mon, Dec 5, 2016 at 10:08 AM, Nicolas Dechesne
<nicolas.dechesne at linaro.org> wrote:
> On Mon, Dec 5, 2016 at 10:10 AM, Paulo Neves <ptsneves at gmail.com> wrote:
>> Sorry for my ambiguity. When I mentioned binaries I meant general
>> binary data, not necessarily executable. Their only need is that the
>> new recipe needs to be fed these data from the other package so it can
>> produce it's own output. This binary data only needs to be available
>> in the host pc, in the recipe bake.
>
> in that case, i suppose you can consider these 'binary files' as
> development files like other .h or libs, and package them in the -dev
> package of the dependency. You can control which files get into the
> -dev package using FILES_${PN}-dev in your recipe.