On Mon, 2018-06-18 at 13:07 -0400, Mark Asselstine wrote: > On Monday, June 18, 2018 12:51:47 PM EDT Andreas Müller wrote: > > On Mon, Jun 18, 2018 at 4:45 PM, Mark Asselstine > > My builds have remove-libtool enabled so I did not see this QA > > warning/error. > > > > Isn't remove-libtool enabled by default since pyro/2.3 - so that > > this > > patch is obsolete (and all the other same kind coming later)? > > The documentation still indicates: > --- > <note> > The <filename>remove-libtool</filename> class is not > enabled by > default. > </note> > --- > > So as far as I know this still needs to be handled recipe to recipe > by inheriting the remove-libtool class in the affected recipes. I > have done builds without manipulating the generated local.conf which > seem to confirm this but I could be wrong. Add RP who might have > some guidance.
Removing the libtool files became the project default a while ago (Jan 2017): meta/conf/distro/defaultsetup.conf:INHERIT_DISTRO ?= "debian devshell sstate license remove-libtool" so I suspect you're in the minority not using that now. http://git.yoctoproject.org/cgit.cgi/poky/commit/meta/conf/distro/defaultsetup.conf?id=3e2a47fdfceccd5f8832235b7a2df83076e84a98 Cheers, Richard -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
