From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][dizzy]Update PyQt and related recipes
Date: Mon, 02 Mar 2015 15:49:10 -0500 [thread overview]
Message-ID: <54F4CCC6.7070107@balister.org> (raw)
In-Reply-To: <CAP9ODKojHgfGhYNBRwkCHNdA_1Rp+JuFLSu0tz7D5iUTMjYoKA@mail.gmail.com>
On 02/27/2015 04:37 PM, Otavio Salvador wrote:
> On Fri, Feb 27, 2015 at 5:42 PM, Philip Balister <philip@balister.org> wrote:
>> On 02/27/2015 12:31 AM, Martin Jansa wrote:
>>> On Tue, Feb 24, 2015 at 04:46:48PM -0800, Philip Balister wrote:
>>>> Please pull these three patches into meta-oe/dizzy.
>>>>
>>>> https://github.com/openembedded/meta-oe/pull/19
>>>>
>>>> These lead to a working PyQt4, which will reduce the number of questions
>>>> I get about gnuradio-companion not working on dizzy.
>>>
>>> I'm not sure if we should do upgrades in release branch which should
>>> receive only bug fixes, but I'll let daisy maintainers to decide.
>>
>> Basically, what is in dizzy doesn't work for anyone. To make it work, we
>> need to upgrade to pickup some changes that made pyqt easier to cross
>> compile.
>
> Yes, this is why I support this update however we need to fix the sip
> upgrade path.
>
What's wrong with the sip update path? Originally, there was only a
recipe for sip-native, this patch replaces the sip-native recipe with
one that works for native and target.
Philip
next prev parent reply other threads:[~2015-03-02 20:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 0:46 [meta-oe][dizzy]Update PyQt and related recipes Philip Balister
2015-02-25 18:29 ` Otavio Salvador
2015-02-27 8:31 ` Martin Jansa
2015-02-27 13:41 ` Otavio Salvador
2015-03-10 20:53 ` akuster808
2015-03-10 20:54 ` Philip Balister
2015-03-18 15:21 ` akuster808
2015-03-26 21:39 ` Philip Balister
2015-02-27 20:42 ` Philip Balister
2015-02-27 21:37 ` Otavio Salvador
2015-03-02 20:49 ` Philip Balister [this message]
2015-03-02 20:56 ` Otavio Salvador
2015-03-02 22:05 ` Philip Balister
2015-03-02 22:19 ` Otavio Salvador
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=54F4CCC6.7070107@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.