Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Laszlo Papp <lpapp@kde.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] Yocto: Install full set of python modules in Qt SDK toolchain
Date: Thu, 18 Sep 2014 11:30:36 +0200	[thread overview]
Message-ID: <201409181130.36388.marex@denx.de> (raw)
In-Reply-To: <CAOMwXhN5=zy_wkKypAMjaPxTY1ezCZ302L8hqokNZQaUBbcfNQ@mail.gmail.com>

On Thursday, September 18, 2014 at 11:23:13 AM, Laszlo Papp wrote:
> On Thu, Sep 18, 2014 at 10:16 AM, Marek Vasut <marex@denx.de> wrote:
> > On Thursday, September 18, 2014 at 11:11:45 AM, Laszlo Papp wrote:
> >> Come on, Yocto maintainers, please...
> >> 
> >> Mark sent this change relatively long ago, and it is still in "new"
> >> state, sadly. The current SDK shipped _breaks_ any third-party
> >> software that uses standard python with regards to the libraries and
> >> all that.
> >> 
> >> This is is slightly frustrating. We also face the same issue. :(
> > 
> > Thanks for the reminder, new version which should fix the issues with the
> > previous one is on the ML now. You're all on CC.
> 
> I do not think this is an explicit Qt issue, and hence fixing on that
> layer sounds like a weird approach. It seems to be a generic python
> issue and so, I think it should be addressed in its core. I opened a
> new report for this:
> 
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=6735

Then you probably want to add nativesdk-packagegroup-python class into the other 
toolchain recipes as well . Or even better, into the base SDK toolchain class 
(is there one?)

Best regards,
Marek Vasut


  reply	other threads:[~2014-09-18  9:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-07 19:10 [PATCH] Yocto: Install full set of python modules in Qt SDK toolchain Marek Vasut
2014-08-08  5:22 ` Koen Kooi
2014-08-08 12:22   ` Marek Vasut
2014-08-11 10:26     ` Richard Purdie
2014-08-11 18:26       ` Marek Vasut
2014-09-18  9:11         ` Laszlo Papp
2014-09-18  9:12           ` Laszlo Papp
2014-09-18  9:16           ` Marek Vasut
2014-09-18  9:23             ` Laszlo Papp
2014-09-18  9:30               ` Marek Vasut [this message]
2014-09-18 10:29                 ` Laszlo Papp
2014-09-18 13:36                   ` Richard Purdie
2014-09-19  7:14                     ` Marek Vasut
2014-09-19  7:25                       ` Richard Purdie
2014-09-21 16:02                         ` Marek Vasut
2014-11-27 18:07                           ` Laszlo Papp
2014-12-01 15:05                           ` Burton, Ross
2014-12-01 15:13                             ` Richard Purdie
2014-12-01 15:20                               ` Burton, Ross
2014-12-01 15:21                               ` Paul Eggleton
2014-12-01 16:44                                 ` Burton, Ross
2014-12-01 18:04                                   ` Laszlo Papp

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=201409181130.36388.marex@denx.de \
    --to=marex@denx.de \
    --cc=koen@dominion.thruhere.net \
    --cc=lpapp@kde.org \
    --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