From: Martin Jansa <martin.jansa@gmail.com>
To: "Michael Burgett -X (burgetm - CLEARPATH WORKFORCE MANAGEMENT
INC@Cisco)" <burgetm@cisco.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-qt5] qmake5_base.bbclass question
Date: Tue, 18 Feb 2014 14:43:47 +0100 [thread overview]
Message-ID: <20140218134347.GK4067@jama> (raw)
In-Reply-To: <2890E9321F60574296094E33AB39D3C320EFC4E5@xmb-aln-x09.cisco.com>
[-- Attachment #1: Type: text/plain, Size: 1524 bytes --]
On Tue, Feb 18, 2014 at 01:05:10PM +0000, Michael Burgett -X (burgetm - CLEARPATH WORKFORCE MANAGEMENT INC at Cisco) wrote:
> Hello Martin,
Hello Michael,
> I'm working on incorporating the meta-qt5 layer in a yocto tree here at Cisco, and have run into an issue. Being new to Yocto and Qt, I don't trust myself to know if I'm correctly analyzing my problem, and hope you don't mind the intrusion.
Please use openembedded-devel@lists.openembedded.org for generic
questions like this, use [meta-qt5] tag (like README suggests for
sending patches).
> The symptom I am getting is that when I build qt apps in yocto, after the qt5 stuff has all been built, it looks in the wrong place for the include files. It's searching in the sysroot /usr/include, instead of sysroot/usr/include/qt5.
>
> I changed a line in qmake5_base.bbclass:
>
> Headers = ${OE_QMAKE_PATH_HEADERS} => Headers = ${OE_QMAKE_PATH_QT_HEADERS}
>
> so the line in the created qt.conf would be
>
> Headers = /usr/include/qt5 instead of Headers = /usr/include
>
> and this solves my problem.
>
> Is this line incorrect, or do I have another configuration problem somewhere, causing this problem?
It's correct, the reason is that not every qmake built project actually
needs to use Qt headers, so they are not included by default, see
https://github.com/meta-qt5/meta-qt5/wiki/Building-with-OE#wiki-bad-include-paths-and-build-failing-to-find-qt5-headers
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
parent reply other threads:[~2014-02-18 13:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <2890E9321F60574296094E33AB39D3C320EFC4E5@xmb-aln-x09.cisco.com>]
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=20140218134347.GK4067@jama \
--to=martin.jansa@gmail.com \
--cc=burgetm@cisco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.