All of lore.kernel.org
 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 13:17:36 +0100	[thread overview]
Message-ID: <1442698.2y5IVPznBc@helios> (raw)
In-Reply-To: <CABuzA3N_Bk0_AnC3sF4TDqk08F2h2LHcv3ChkWJi4iX=dCKT_g@mail.gmail.com>

On Monday 10 June 2013 12:19:48 John Stirling wrote:
> The Qt application (qtui) is compiled and has some C++, some QML and needs
> to use dbus. I am kicking it off via './qtui -qws'.
> 
> So basically if I had this -
> 
> IMAGE_INSTALL += " \
> qt4-embedded \
> qtui \
> "
> 
> You suggest just cutting it down to
> 
> IMAGE_INSTALL += " \
> qtui \
> "
> and it should work itself out ?

Apart from plugins and anything else that your application doesn't get 
directly linked to, yes.

> I am not entirely sure on the 'inherit qt4e' line.

You do want this here, yes.

> SRC_URI = "git://${SOURCE_REPO}/git/${PN}.git;protocol=ssh;tag=${PV}"

I think you probably should specify SRCREV here, even if it's SRCREV = 
"${AUTOREV}" to build the latest version on the specified branch. For tags that 
won't change, typically we recommend that you specify the full sha1 hash in 
SRCREV and then the system knows it doesn't need to query the git server to 
get the current hash corresponding to the tag.

> PROVIDES = "${PN}_${PV}"

This should not be necessary.

> DEPENDS = "qt4-embedded"

This is already done for you by inheriting qt4e.

> RPROVIDES = "qtui_${PV}"

This should not be necessary either.

> PACKAGES="${PN}"

Unless you have a good reason to do this I would recommend not doing so; the 
standard package splitting should work for most situations and for those where 
it needs to be tweaked slightly that can be done fairly easily.

> FILES_${PN} += "/root/qtui /usr/share/reciva/qml/qtui
> ${sysconfdir}/dbus-1/system.d/"

Typically you would install binaries such as this to ${bindir} rather than 
/root.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  parent reply	other threads:[~2013-06-10 12:17 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 [this message]
2013-06-10 13:46       ` John Stirling
2013-06-10 14:03         ` Paul Eggleton
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=1442698.2y5IVPznBc@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 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.