Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Jeremy Lainé" <jeremy.laine@bolloretelecom.eu>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Dropping qtopia-core-4.3.3.bb and qtopia4core.bbclass
Date: Tue, 24 Mar 2009 12:56:29 +0100	[thread overview]
Message-ID: <49C8CA6D.6010703@bolloretelecom.eu> (raw)
In-Reply-To: <1d6c95c90903201026g709b2adfja5f5a6f8384cc798@mail.gmail.com>

> In the same build that you cross-compile qt4-x11-free, you can compile
> native qt-tools (qmake/moc/uic/rcc), just using properly 'platform'
> and 'xplatform' configure flags and two different specs.

Absolutely, I have always wondered why this was done separately in OE. Another advantage
of doing this is that you will always have the right "qmake" to go with your headers/libs.

> I already created qt4.bbclass that is based on qt4/qt_*.inc and do all
> the required work to build qt. The native qt tools binaries and the
> specs are being sent to staging and a new qmake.bbclass are using them
> to build qmake based applications.

I would be interested in getting hold of a your qt4.bbclass, even if it's not 100%
finished and working with you on it. Let me know if you are available for a chat on IRC.

Cheers,
-- 
Jeremy LAINE
Bolloré telecom | 11bis, rue Scribe | F-75009 Paris



  parent reply	other threads:[~2009-03-24 11:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-17 13:22 Dropping qtopia-core-4.3.3.bb and qtopia4core.bbclass Jeremy Lainé
2009-03-17 13:35 ` Michael 'Mickey' Lauer
2009-03-17 14:03   ` Jeremy Lainé
2009-03-17 21:17     ` Jim Sheldon
2009-03-18 14:40       ` Jeremy Lainé
2009-03-18 15:29         ` Michael 'Mickey' Lauer
2009-03-18 15:49         ` Koen Kooi
2009-03-20 17:26           ` Aloisio Almeida
2009-03-23  4:12             ` Otavio Salvador
2009-03-24 11:56             ` Jeremy Lainé [this message]
2009-03-24 13:11               ` Holger Schurig
2009-03-24 19:57       ` Jeremy Lainé
2009-03-24 22:04         ` Jim Sheldon

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=49C8CA6D.6010703@bolloretelecom.eu \
    --to=jeremy.laine@bolloretelecom.eu \
    --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