From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: wanting to clarify HOSTTOOLS and HOSTTOOLS_NONFATAL
Date: Wed, 29 Mar 2017 11:30:06 +0100 [thread overview]
Message-ID: <1490783406.13980.310.camel@linuxfoundation.org> (raw)
In-Reply-To: <alpine.LFD.2.20.1703290555150.2895@uk63952.mitel.com>
On Wed, 2017-03-29 at 05:56 -0400, Robert P. J. Day wrote:
> On Wed, 29 Mar 2017, Robert P. J. Day wrote:
>
> >
> > again, trying to catch up with new developments, and i want to
> > make sure i understand these variables. as i read it (and i could
> > be
> > off-base), HOSTTOOLS represents a list of tools that *must* be
> > available one way or the other, and any tools listed there are
> > allowed to be symlinked from the tools available in PATH, is that
> > correct?
> >
> > OTOH, HOSTTOOLS_NONFATAL represents whitelisted tools that will
> > be
> > symlinked if they're there, but their absence is not fatal.
Correct. Perhaps you could send a patch to add these to the manual? :)
> > i'm still not totally clear here ... and there is no mention of
> > these variables in the YP reference manual variables glossary.
> oh, i think i asked this before as well ... how do these variables
> relate to ASSUME_PROVIDED? IIRC, ASSUME_PROVIDED is interpreted as "i
> have these utilities on my host, use them."
ASSUME_PROVIDED means that if something does DEPENDS += "x" and x is in
ASSUME_PRODIDED, bitbake won't try and build it or require a recipe for
it.
HOSTTOOLS is about filtering out tools from PATH for determinism.
Its unfortunate there is overlap between these but both are good things
to have in their own rights and I don't really see a way to automate it
in a 100% accurate way.
Cheers,
Richard
next prev parent reply other threads:[~2017-03-29 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 9:54 wanting to clarify HOSTTOOLS and HOSTTOOLS_NONFATAL Robert P. J. Day
2017-03-29 9:56 ` Robert P. J. Day
2017-03-29 10:30 ` Richard Purdie [this message]
2017-03-29 10:40 ` Robert P. J. Day
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1490783406.13980.310.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.