All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Christian Gagneraud <chgans@gna.org>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: [Qt5] mkspecs/devices: beagleboard == am335x ?
Date: Fri, 26 Jul 2013 17:06:41 -0400	[thread overview]
Message-ID: <20130726210641.GF3558@edge> (raw)
In-Reply-To: <51F1AA6E.4050607@gna.org>

On Fri, Jul 26, 2013 at 10:45:02AM +1200, Christian Gagneraud wrote:
> Hi there,
> 
> In qtbase sources, there are a couple of "device" definitions files,
> according to [1], this greatly help cross-compiling qt5.
> This device file specify things for CPU and GPU optimisations. So
> basically these files are tightly coupled with BSP providers.
> 
> One of them is linux-beagleboard-g++ [2], is it appropriate to use
> this one for AM335x based platform as well?
> 
> The meta-qt5 layer doesn't seem to use this feature, but if it did,
> would this device config files help to get an optimised Qt5 build
> for TI SoCs? Especially, would that help to get OpenGL stuff sorted
> out?
> 
> Regards,
> Chris
> 
> [1] http://blog.qt.digia.com/blog/2012/04/13/cross-compiling-qt-for-the-masses/
> [2] https://qt.gitorious.org/qt/qtbase/trees/stable/mkspecs/devices/linux-beagleboard-g++

Chris,

Looking at those files shows very basic compiler optimization flags being set, 
-march, -mtune, -mfpu etc. I don't see any GL or GPU specifics in there. It 
also hardcodes things like soft-fp, which is not good. All this stuff is 
alredy taken care of by the build framework and I'm sure meta-qt5, like the 
old qt4, sets all the right COMPILER_FLAGS to get the most performance from 
the target CPU.

-- 
Denys


  reply	other threads:[~2013-07-26 21:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25 22:45 [Qt5] mkspecs/devices: beagleboard == am335x ? Christian Gagneraud
2013-07-26 21:06 ` Denys Dmytriyenko [this message]
2013-07-27  2:20   ` Sundareson, Prabindh
2013-07-27 15:18     ` Christian Gagneraud
2013-07-27  3:41       ` Denys Dmytriyenko
2013-07-27 20:05         ` Christian Gagneraud

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=20130726210641.GF3558@edge \
    --to=denys@ti.com \
    --cc=chgans@gna.org \
    --cc=meta-ti@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.