On Wed, Nov 1, 2017 at 8:35 AM, Konrad Scherer <[email protected]> wrote: > On 10/31/2017 03:15 AM, Markus Lehtonen wrote: >> Please see the 6th patch ("devtools/images: add python-pgo-image") in my >> patchset for python-pgo-image. >> >> I'd like the profiling to work out-of-the-box, without requiring some >> strange-ish (i.e. modification of HOSTTOOLS) changes in local.conf. >> The required utilities, ip and scp, are rather standard tools, >> anyway. And, they used to be in HOSTTOOLS, unconditionally, before. > > ip and scp are not needed for a normal build so it doesn't make sense to > make them mandatory.
Shouldn't the preferred approach be to use -native tools whenever possible? It solves the problem of needing to add obscure tools into HOSTTOOLS and also makes tests more reproducible by ensuring that they always run with a known version of a particular tool, not something which may be host specific. > Including them unconditionally caused build failures > for us because the docker images we use for coverage builds did not include > those binaries. I realize that doing builds in minimal containers is rare > today, but I expect it to become more common. It's not so uncommon, even now. > Since the recipe uses the oeqa helpers, is there a way to setup the > conditional inclusion to detect this and include the required binaries in > HOSTTOOLS? Or have the oeqa helper modify the HOSTTOOLS before they are > used? > > > -- > Konrad Scherer, MTS, Linux Products Group, Wind River > -- > _______________________________________________ > Openembedded-core mailing list > [email protected] > http://lists.openembedded.org/mailman/listinfo/openembedded-core -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
