Hi Marek, On Friday 19 September 2014 18:27:30 Marek Vasut wrote: > On Friday, September 19, 2014 at 06:13:46 PM, Christopher Larson wrote: > > On Fri, Sep 19, 2014 at 12:06 AM, Marek Vasut <[email protected]> wrote: > > > On Thursday, September 18, 2014 at 03:30:11 PM, Richard Purdie wrote: > > > > On Thu, 2014-09-18 at 11:15 +0200, Marek Vasut wrote: > > > > > Introduce and use nativesdk-packagegroup-python , which contains all > > > > > necessary python components for the native SDK. Make use of this > > > > > package group in buildtools-tarball.bb immediatelly. > > > > > > > > Specifically, isn't this the list of packages needed to run bitbake > > > > and > > > > its associated utils? "python" isn't therefore a particularly good > > > > description of this package? > > > > > > This is really just and only python packages, nothing else. > > > > The fact that it only contains python packages doesn't mean it contains > > all > > python packages, or is somehow generic. It's a specific subset of python > > modules used by bitbake. > > OK, so uh, what would be the right solution here to make the toolchain > usable? As I am no expert, I really don't know what to do now. Can you help > please ?
There's clearly a bug here, adding a Python-using component does not mean you should have python in the SDK but that's what currently happens. There is a bug open now covering this, we will do our best to address it in a timely manner. (FWIW, I would have thought this issue has been present for some time rather than being a recent regression.) In the mean time however you can work around it by adding nativesdk-python-modules (an existing meta-package) to your SDK via TOOLCHAIN_HOST_TASK. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
