Hi,
Hosttools are set after the bitbake configuration is parsed so there is no way
to affect the outcome from the "recipe space". HOSTTOOLS can only be set from
bitbake configuration. Thus, I don't see any way to conditionally expand the
value in case something specific is being built.
The only way that I can think of to make this somehow work would be to add the
utilities to HOSTTOOLS_NONFATAL. Then, the utils would be linked if present and
the profile task would succeed on most systems.
Thanks,
Markus
On 01/11/2017, 17.35, "Konrad Scherer" <konrad.sche...@windriver.com> wrote:
On 10/31/2017 03:15 AM, Markus Lehtonen wrote:
> Hi,
>
> 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. 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.
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
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
