Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Anders Darander <anders@chargestorm.se>
To: <openembedded-devel@lists.openembedded.org>
Cc: Anders Darander <anders@chargestorm.se>
Subject: [meta-qt5][PATCH 0/1] Add OE_QMAKE_INCDIR_QT
Date: Mon, 27 Oct 2014 12:31:31 +0100	[thread overview]
Message-ID: <cover.1414409458.git.anders@chargestorm.se> (raw)

This adds OE_QMAKE_INCDIR_QT to the variables in qmake5_base.bbclass.

Qt4 in oe-core exports this variables, both in their qt4 bbclasses as well
as in their SDK. As a result, recipes like e.g. qextserialport [1] in meta-oe, 
uses OE_QMAKE_INCDIR_QT in the generated extserialport.prf file, in order 
allow both bitbake build recipes and applications build using the SDK, 
find the header filer of qextserialport.

In Qt5, OE_QMAKE_INCDIR_QT is not set when building using bitbake, however, 
that variable is still set in the environment file for the generated SDK.

Thus, to make the use case in e.g. [1] work also for Qt5, we'll add this 
variable to qmake5_base.bbclass. This will sync up the two use-cases.

[1] http://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-qt/qextserialport/qextserialport_1.2rc.bb

The following changes since commit 9a4c0b393bf031acace5c2cc00d625a24c639d1c:

  maliit-framework-qt5: Update SRCREV (2014-10-21 15:33:05 +0200)

are available in the git repository at:

  git://github.com/darander/meta-qt5 9a0b3d2f7e1ac7e854430fe1e93271c71f574083
  https://github.com/darander/meta-qt5/tree/qtsdk

Anders Darander (1):
  qmake5: set OE_QMAKE_INCDIR_QT

 classes/qmake5_base.bbclass | 1 +
 1 file changed, 1 insertion(+)

-- 
2.1.1



             reply	other threads:[~2014-10-27 11:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27 11:31 Anders Darander [this message]
2014-10-27 11:31 ` [meta-qt5][PATCH 1/1] qmake5: set OE_QMAKE_INCDIR_QT Anders Darander
2014-12-01  9:41   ` Anders Darander
2014-12-01 15:27   ` 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=cover.1414409458.git.anders@chargestorm.se \
    --to=anders@chargestorm.se \
    --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