From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: qt4*-image and qt 4.6.3?
Date: Wed, 02 Feb 2011 09:40:41 -0700 [thread overview]
Message-ID: <4D498909.90908@mentor.com> (raw)
Hey all,
Currently none of the qt4*-images build for qt4 4.6.3. This is because
building with -xmlpatterns in 4.6.3 isn't viable (it's not a trivial fix
to enable it, for some reason...) and it's embedded into the image
recipes themselves in some cases, rather than tasks that can be
RRECOMMENDED. I see two courses of action here:
1) Just say the images don't build on 4.6.x (and I'll drop trying them
from my builder)
2) Rework the qt4e-*images to use a new task-qt4e-base and update
task-qt4-x11 to RRECOMMEND the xmlpattern bits.
Currently angstrom-2008.1 and kaelios-2009 pin to 4.6.3 and are in-tree
(and I know Arago also cares, but is out of tree and I'm not suggesting
we drop qt 4.6.x). Thoughts? Thanks!
--
Tom Rini
Mentor Graphics Corporation
next reply other threads:[~2011-02-02 16:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 16:40 Tom Rini [this message]
2011-02-02 19:14 ` qt4*-image and qt 4.6.3? Holger Freyther
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=4D498909.90908@mentor.com \
--to=tom_rini@mentor.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox