Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: John Stirling <ap.john.stirling@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: qt4-embedded - image size
Date: Mon, 10 Jun 2013 15:03:44 +0100	[thread overview]
Message-ID: <1742399.JSmCq3b5r2@helios> (raw)
In-Reply-To: <CABuzA3OXwzQBeYJ4D5kGYANTNykOPnOR4BDrj3=y9TauD1Z5hg@mail.gmail.com>

On Monday 10 June 2013 14:46:57 John Stirling wrote:
> Looking fairly promising so far. Image size down from 280Mb to 90Mb and
> only Qt related stuff now seems to be in /usr/lib/
> 
> The font's seem to be missing though -
> QFontDatabase: Cannot find font directory /usr/lib/fonts - is Qt installed
> correctly?
> We won't need all the fonts in any case but would you expect them to have
> been pulled in automatically ?

Right, for Qt/E if you are displaying any text you'll need to explicitly 
install the package for this since nothing depends upon it. You can install 
the qt4-embedded-fonts package which brings in all fonts that are distributed 
with Qt, or alternatively you can install only the fonts you want (qt4-
embedded-fonts-ttf-vera, etc.)
 
> Pretty sure I need the first 3, but not sure about the rest. Does that look
> about right to you size wise ? We're just trying to tie down flash sizes at
> the moment and want to get a fairly accurate estimate for Qt.

This looks reasonable to me. Note however if you start changing some of the 
build-time configuration options for Qt you may be able to disable a few things 
you don't need. Have a look at Qt's configuration options [1]. You can see 
exactly which options are being used to build Qt with:

bitbake -e | grep "^QT_CONFIG_FLAGS="

If you search for QT_CONFIG_FLAGS under meta/recipes-qt/qt4/ you'll see how 
this variable gets set.

> I guess also at some point we might want to switch to Qt5. Is that
> comparable in size ?

Not sure I'm afraid, although I believe it is more modular so in theory you 
should be able to cut out more pieces you don't need.

Cheers,
Paul

[1] http://qt-project.org/doc/qt-4.8/configure-options.html

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2013-06-10 14:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-10 10:31 qt4-embedded - image size John Stirling
2013-06-10 10:55 ` Paul Eggleton
2013-06-10 11:19   ` John Stirling
2013-06-10 12:10     ` Nicolas Dechesne
2013-06-10 12:59       ` Eric Bénard
2013-06-10 13:07         ` Nicolas Dechesne
2013-06-10 13:13           ` Eric Bénard
2013-06-10 16:37             ` Paul Eggleton
2013-06-10 12:17     ` Paul Eggleton
2013-06-10 13:46       ` John Stirling
2013-06-10 14:03         ` Paul Eggleton [this message]
2013-06-10 16:20           ` John Stirling

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=1742399.JSmCq3b5r2@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=ap.john.stirling@gmail.com \
    --cc=openembedded-core@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