On 07/06/2018 03:06 PM, Raymond Yeung wrote: > I've changed the subject heading to make it more specific to our problem. > Hopefully this generates some responses. > > > It has been blocking us for close to one week now. We want to use our 3rd > party vendor openssl, not the one that comes with the source. Apparently, > even with "minimal" instead of "base" or "sato" cannot exclude it. > > > Any idea [e.g. how do we systematically find out how it's included now, and > possibly what other packages/recipes we may also need to remove due to > dependency]?
I tend to use the ouput of the buildhistory class when I have these questions. Philip > > > Thanks, > > Raymond > > > ________________________________ > From: Raymond Yeung <rksye...@hotmail.com> > Sent: Monday, July 2, 2018 11:05 PM > To: yocto@yoctoproject.org > Subject: How to remove a package from a build > > > We've our own non-yocto openssl that we want to use. At the moment, we're > using "sato" image, rather than "minimal" and includes its openssl that is > out-of-date. What is the best way to exclude it from our image (and from > sysroots)? > > > We have thought about two ideas - > > > 1. Use smaller image like core-image-base, or core-image-full-cmdline (but > not -minimal that may remove too much functionality). > 2. Use INSTALL_IMAGE_remove += " openssl" > > > Would either one work? Also, how do I follow the .bb files etc (e.g. > starting from the one for sato) to trace down which sub-package includes > openssl? > > > Thanks, > > Raymond > > > -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
