From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 0/8] Add meta-toolchain-qte from OE
Date: Thu, 20 Jan 2011 13:50:07 +0000 [thread overview]
Message-ID: <201101201350.07758.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <CF53CD96-5C74-4422-B442-2837C6325B9A@dominion.thruhere.net>
On Thursday 20 January 2011 12:17:39 Koen Kooi wrote:
> > * I notice qt4.inc specifies -embedded in the configure command line and
> > then qt4-x11-free adds -no-embedded. Is it really a good idea to be
> > specifying - embedded and -no-embedded at the same time?
>
> That's a leftover, and should be safe to eliminate. We do need to specify
> -embedded in qt4-tools to avoid some extra build deps.
Yep I saw that in the tools recipe, makes sense there. I will see about
adjusting the inc files for Qt4 itself.
> I personally do not know of any, but I didn't want to loose features at
> this point. I'm OK dropping it from QT, but other software in OE sadly
> hasn't caught the sqlite3 train yet, so having sqlite2 in a layer
> somewhere is unavoidable.
I was just curious really. I can imagine there are commercial users of it out
there still, and if we want to bring in an "end-user" app that requires it
then of course we would need to bring it across also. A cursory search of OE
brings up at least this list:
* asterisk
* balsa
* gpe
* prismstumbler
* txdrug
Of those, I think the only ones of real concern for meta-openembedded are gpe
and prismstumbler (balsa and asterisk can apparently be built using sqlite3,
assuming there are no problems converting existing databases.)
Cheers,
Paul
next prev parent reply other threads:[~2011-01-20 13:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 16:54 [PATCH 0/8] Add meta-toolchain-qte from OE Paul Eggleton
2011-01-17 16:54 ` [PATCH 1/8] Add directfb 1.4.6 from OpenEmbedded Paul Eggleton
2011-01-17 16:54 ` [PATCH 2/8] qt4: add qt4-embedded 4.6.3 " Paul Eggleton
2011-01-17 16:54 ` [PATCH 3/8] glib-2.0: extend to nativesdk Paul Eggleton
2011-01-17 16:54 ` [PATCH 4/8] dbus: " Paul Eggleton
2011-01-17 16:54 ` [PATCH 5/8] Add qt4-tools-nativesdk 4.6.3 based on qt4-tools-sdk from OpenEmbedded Paul Eggleton
2011-01-17 16:54 ` [PATCH 6/8] package.bbclass: add nodeprrecs flag to RRECOMMENDS_pkgname Paul Eggleton
2011-01-17 16:54 ` [PATCH 7/8] avahi: prevent unnecessary runtime dependency on gtk+ Paul Eggleton
2011-01-17 16:54 ` [PATCH 8/8] Add meta-toolchain-qte and dependent tasks from OpenEmbedded Paul Eggleton
2011-01-17 17:14 ` [PATCH 0/8] Add meta-toolchain-qte from OE Koen Kooi
2011-01-17 17:39 ` Paul Eggleton
2011-01-17 17:49 ` Koen Kooi
2011-01-19 12:51 ` Paul Eggleton
2011-01-19 13:15 ` Koen Kooi
2011-01-20 12:06 ` Paul Eggleton
2011-01-20 12:17 ` Koen Kooi
2011-01-20 13:50 ` Paul Eggleton [this message]
2011-01-18 20:25 ` Saul Wold
2011-01-20 15:09 ` Paul Eggleton
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=201101201350.07758.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--cc=poky@yoctoproject.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