From: Anders Darander <anders@chargestorm.se>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 00/10] qt4: upgrade to 4.8.3 and cleanup
Date: Fri, 28 Sep 2012 08:37:56 +0200 [thread overview]
Message-ID: <20120928063756.GA21472@ad.chargestorm.se> (raw)
In-Reply-To: <20120927154530.GE3454@jama.jama.net>
* Martin Jansa <martin.jansa@gmail.com> [120927 17:44]:
> On Thu, Sep 27, 2012 at 04:10:20PM +0100, Paul Eggleton wrote:
> > On Thursday 27 September 2012 00:27:05 Martin Jansa wrote:
> > > Please test on more architectures.
> > > I've tested complete qt4-native + qt4-free-x11 on armv4t.
> > > And only do_patch for nativesdk-qt4-tools, qt-mobility-*, qt4-embedded.
> >
> > So this is great work and these patches look good, although I'm still not
> > particularly happy with breaking out so many of the configure options because
> > I'm convinced it won't stop here; but it's possible I might be overruled on
> > this issue.
> I've added that, because meta-webos layer disables more stuff then .inc
> file forces enabled, so I would have to rewrite whole QT_CONFIG_FLAGS
> (if I don't want to have e.g. -webkit from .inc and -no-webkit appended
> after that through QT_DISTRO_FLAGS).
> But it can be just 2 variables instead of 6 if it's issue.
I haven't looked closely at the patches, but we're also disabling lots
of stuff (though, quite a bit of that comes from meta-oe). Thus, I'm
leaning towards an easier way to handle this.
We're currently using an approach were we add to QT_CONFIG_FLAGS, to set
our desired config, and oe_filter_out() to remove certain defaults from
oe-core and meta-oe. Thus, everything that can help reduce this mess is
something we'd appreciate.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
next prev parent reply other threads:[~2012-09-28 6:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 22:27 [PATCH 00/10] qt4: upgrade to 4.8.3 and cleanup Martin Jansa
2012-09-26 22:27 ` [PATCH 01/10] qt4-tools-nativesdk.inc: rename to nativesdk-qt4-tools.inc Martin Jansa
2012-09-26 22:27 ` [PATCH 02/10] qt4: use releases.qt-project.org instead of get.qt.nokia.com Martin Jansa
2012-09-26 22:27 ` [PATCH 03/10] qt4: rename qt-4.8.1 to qt4-4.8.1 to match other .inc and .bb Martin Jansa
2012-09-26 22:27 ` [PATCH 04/10] qt4.inc: move more options to separate variables Martin Jansa
2012-09-26 22:27 ` [PATCH 05/10] qt-mobility: move qt-mobility patches to separate dir Martin Jansa
2012-09-26 22:27 ` [PATCH 06/10] qt4: move patches from files to qt4-4.8.1 Martin Jansa
2012-09-26 22:27 ` [PATCH 07/10] qt4: drop patches not used in any recipe Martin Jansa
2012-09-26 22:27 ` [PATCH 08/10] qt4: replace all local patches with git patches with headers Martin Jansa
2012-09-26 22:27 ` [PATCH 09/10] qt4: PR bumps Martin Jansa
2012-09-26 22:27 ` [PATCH 10/10] qt4: upgrade to 4.8.3 Martin Jansa
[not found] ` <cover.1349134104.git.Martin.Jansa@gmail.com>
2012-10-01 23:28 ` [PATCHv2 10/10] qt4: add 4.8.3 version with negative D_P Martin Jansa
2012-09-27 15:10 ` [PATCH 00/10] qt4: upgrade to 4.8.3 and cleanup Paul Eggleton
2012-09-27 15:45 ` Martin Jansa
2012-09-28 6:37 ` Anders Darander [this message]
2012-09-28 16:43 ` Martin Jansa
2012-09-30 20:18 ` Martin Jansa
2012-10-01 14:31 ` Martin Jansa
2012-10-01 23:26 ` Martin Jansa
2012-10-02 8:29 ` Martin Jansa
2012-10-03 1:40 ` Saul Wold
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=20120928063756.GA21472@ad.chargestorm.se \
--to=anders@chargestorm.se \
--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