On 18 September 2014 03:21, Ong, Boon Leong <[email protected]> wrote: >> On their own, the DPDK packages are useless as the user needs to compile >> their application with them. What you're basically doing is forcing a >> library onto >> *every* image for that machine, even ones that don't want to use DPDK. >> Please don't do that. > > So, reading from your feedback, I think that you are suggesting to create > bbappend file for each of the target image type > (core-image-sato & core-image-sato-sdk) with IMAGE_INSTALL += "dpdk > dpdk-examples" ... > Just want to be sure we get your idea correctly. > > These are the two images that CID customers are using from Yocto Project.
I'm suggesting that nobody will be taking e.g core-image-sato and be able to work out of the box with dpdk installed, as they'll need a toolchain to build their own application against dpdk. Let's just not install it in the images, and a user will either write a recipe for their image or create a SDK image to which they can trivially add dpdk. Ross -- _______________________________________________ meta-intel mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-intel
