From: Patrick Ohly <patrick.ohly@intel.com>
To: Jonathan Liu <net147@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] bitbake.conf: Add sdl-config to HOSTTOOLS if using host SDL
Date: Tue, 27 Jun 2017 12:38:27 +0200 [thread overview]
Message-ID: <1498559907.7464.42.camel@intel.com> (raw)
In-Reply-To: <CANwerB3jfo=r=xcHdn8+yU1=r9JmK0_3MCnQWdf8uDh=Tn1AGA@mail.gmail.com>
On Tue, 2017-06-27 at 20:24 +1000, Jonathan Liu wrote:
> Hi Patrick,
>
> The original problem was that bitbake would print out the error:
> "libsdl-native is set to be ASSUME_PROVIDED but sdl-config can't be
> found in PATH. Please either install it, or configure qemu not to
> require sdl.", if "libsdl-native" was in ASSUME_PROVIDED even if the
> host has sdl-config in its PATH.
>
> This occurred really early for a clean build and bitbake would bail
> out. The sanity check is in meta/classes/sanity.bbclass.
I've not hit that problem, probably because the sanity check was not run
again when I changed ASSUME_PROVIDED. I can reproduce it in a clean
build directory without conf/sanity_info.
I think extending HOSTTOOLS merely to satisfy sanity.bbclass is the
wrong solution to the problem. It makes sdl-config available to all
recipes, which is unnecessary and potentially introduces back host
contamination.
It is unnecessary because the qemu recipe has special code that enables
the use of the host SDL when told to do so via ASSUME_PROVIDED.
Can you come up with a better solution, probably by patching
sanity.bbclass?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2017-06-27 10:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 12:15 [PATCH v2] bitbake.conf: Add sdl-config to HOSTTOOLS if using host SDL Jonathan Liu
2017-06-27 9:05 ` Patrick Ohly
2017-06-27 9:53 ` Jonathan Liu
2017-06-27 10:02 ` Patrick Ohly
2017-06-27 10:09 ` Burton, Ross
2017-06-27 10:21 ` Patrick Ohly
2017-06-27 10:24 ` Jonathan Liu
2017-06-27 10:38 ` Patrick Ohly [this message]
2017-06-27 11:11 ` Jonathan Liu
2017-06-27 15:50 ` Patrick Ohly
2017-06-27 12:54 ` Richard Purdie
2017-06-27 12:56 ` Jonathan Liu
2017-06-27 13:02 ` Jonathan Liu
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=1498559907.7464.42.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=net147@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox