All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Sergio Borgonovo <mail@webthatworks.it>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: qt5 toolchain
Date: Fri, 9 Oct 2015 22:31:34 +0200	[thread overview]
Message-ID: <56182426.30004@webthatworks.it> (raw)

I've followed the instruction for wanderboard to build an image with qt5 
support for an imx28evk based board.

I had to skip several packages because they depend on opengl.

Still I've been able to bake an image that boot.

Now I was thinking to build the toolchain for qt5.

Reading here and there it seems that I should find qmake in the sysroot 
and some env variable set (after sourcing environment-setup-*)
eg.
http://lists.qt-project.org/pipermail/qbs/2013-November/000563.html

My local.conf is a stripped down version of the one proposed for the 
wonderboard to get rid of the opengl dependencies.

I did
bitbake core-image-minimal -c populate_sdk
but I couldn't find qmake in the sysroot neither the qt related 
variables set.
QT5 headers are where they should be.

I can't bitbake
- meta-toolchain-qte (depends on x11)
- meta-toolchain-qt5 (some packages depends on opengl eg. qt3d)

What is the best way to go further?

BTW is this the right place to ask this kind of questions? It seems more 
a mailing list for the fsl developers rather than fsl users.
If it is not where should I post this kind of questions and more general 
question on yocto?

thanks

-- 
Ivan Sergio Borgonovo
http://www.webthatworks.it



             reply	other threads:[~2015-10-09 20:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-09 20:31 Ivan Sergio Borgonovo [this message]
2015-10-13 13:11 ` qt5 toolchain Otavio Salvador
2015-10-15 16:26   ` Ivan Sergio Borgonovo
2015-10-15 16:48     ` Otavio Salvador
2015-10-15 22:03       ` Ivan Sergio Borgonovo
2015-10-16 13:59         ` 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=56182426.30004@webthatworks.it \
    --to=mail@webthatworks.it \
    --cc=meta-freescale@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 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.