On Tue, 2017-06-27 at 21:11 +1000, Jonathan Liu wrote: > Hi Patrick, > > On 27 June 2017 at 20:38, Patrick Ohly <patrick.o...@intel.com> wrote: > > 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? > > I can't think of any at this stage.
Here's what qemu.inc does: do_configure_prepend_class-native() { # Append build host pkg-config paths for native target since the host may provide sdl BHOST_PKGCONFIG_PATH=$(PATH=/usr/bin:/bin pkg-config --variable pc_path pkg-config || echo "") if [ ! -z "$BHOST_PKGCONFIG_PATH" ]; then export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:$BHOST_PKGCONFIG_PATH fi insanity.bbclass could use the host pkg-config to ensure that sdl.pc is installed. > Feel free to post a patch if you come up with something better. Sorry, I don't have time for that. I've filed https://bugzilla.yoctoproject.org/show_bug.cgi?id=11725 so that we don't forget about it. -- 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. -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core