Re: [meta-qt5] Qt5 recipes question

[Martin Jansa <martin.jansa@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1585 bytes --]

On Wed, Mar 12, 2014 at 05:15:03PM -0700, David Van Beveren wrote:
> Hi Martin,

Hi,

> I noticed you as the maintainer of the Qt5 recipes. I am looking for an

openembedded-devel@lists.openembedded.org is better place to ask
questions like this (with [meta-qt5] in subject) more people are reading
ML and you can get answer faster when I'm not around.

I'll add oe-devel to CC now.

> example or a little guidance. I want to deploy Qt on my embedded box with
> GUI support removed. We have no display hardware available. As you can
> imagine, our embedded target has no GUI.
> 
> We only care about nitove versions of the toolchain pieces (moc, qmake,
> headers, etc), along with base (less GUI), network and QtScript modules.
> 
> My embedded target is a powerful multi-core box and I'm preferring to build
> my app locally there rather than cross compiling.
> 
> My baseline is Dylan. Can you tell me what recipes to add and what other
> configurations I might need to make to stop the GUI from building? I have
> the meta-qt5 repo in my config already.
> 
> Thanks for your help. I think this non-GUI config would be a good example
> or canned recipe as a lot of embedded Qt projects don't have GUI.

With dora and master branches it's easier see PACKAGECONFIGs in qtbase.inc and
you can just disable all options you don't need to strip down the qt.

With dylan you need to set couple of QT_* variables and adjust *DEPENDS
accordingly, but the result should be the same.

Regards,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]