[OE-core] [PATCH 1/2] nativesdk-packagegroup-python: buildtools-tarball: Introduce NativeSDK package group

[Marek Vasut]

On Friday, September 19, 2014 at 06:42:14 PM, Paul Eggleton wrote:
> Hi Marek,

Hi Paul,

> 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 <marex at denx.de> 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.

Thank you, I really appreciate it !

> (FWIW, I would have thought this issue has been present for
> some time rather than being a recent regression.)

Yes, it was. It only hit me recently when U-Boot switched to Kconfig, which 
needs a python module, which is missing from the SDK toolchain though.

> 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.

Ah, thank you for the hint!

Best regards,
Marek Vasut