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.
Thanks Paulo Neves On Mon, Dec 5, 2016 at 8:58 AM, Nicolas Dechesne <nicolas.deche...@linaro.org> wrote: > On Mon, Dec 5, 2016 at 9:54 AM, Paulo Neves <ptsne...@gmail.com> wrote: >> The files form this other package are mostly binaries in a directory >> structure. I have to create an additional package which works with the >> other package's(the dependency) installed directory structure. >> Also you hinted at something I didn't know before, which was that >> packages need to be additionally exported to the sysroot and this was >> typically done through the -dev package. Can you point me at where >> this is documented? I am having a huge difficulty trying to find these >> conventions in the manual or by googling. > > > are the binaries "native" binaries (eg. that are intended to run on > the host PC) or target binaries (libraries) that would want to link > against to build your new package? -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
