All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Liu <net147@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [meta-qt5][PATCH v2 1/2] qtimageformats: allow empty qtimageformats package
Date: Sun, 02 Mar 2014 13:54:46 +1100	[thread overview]
Message-ID: <53129D76.9060802@gmail.com> (raw)
In-Reply-To: <1393729091-12840-1-git-send-email-net147@gmail.com>

On 2/03/2014 1:58 PM, Jonathan Liu wrote:
> This fixes installing qtimageformats-dev with opkg as it depends on the
> qtimageformats package which wasn't created.
>
> The qtimageformats package was not created as it is empty and BitBake
> avoids producing empty packages by default. The installed files consist
> of source files split into qtimageformats-dbg, CMake files split into
> qtimageformats-dev, plugins split into qtimageformats-plugins and
> debug build of plugins split into qtimageformats-plugins-dbg.
>
> Signed-off-by: Jonathan Liu <net147@gmail.com>
> ---
>   recipes-qt/qt5/qtimageformats.inc | 1 +
>   1 file changed, 1 insertion(+)
>
> diff --git a/recipes-qt/qt5/qtimageformats.inc b/recipes-qt/qt5/qtimageformats.inc
> index 1b4bb4f..f90e58a 100644
> --- a/recipes-qt/qt5/qtimageformats.inc
> +++ b/recipes-qt/qt5/qtimageformats.inc
> @@ -1,3 +1,4 @@
>   require qt5.inc
>   
>   DEPENDS += "qtbase tiff"
> +ALLOW_EMPTY_${PN} = "1"
Whoops, wrong mailing list.

Regards,
Jonathan


  reply	other threads:[~2014-03-02  2:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-02  2:58 [meta-qt5][PATCH v2 1/2] qtimageformats: allow empty qtimageformats package Jonathan Liu
2014-03-02  2:54 ` Jonathan Liu [this message]
2014-03-02  2:58 ` [meta-qt5][PATCH v2 2/2] packagegroup-qt5-toolchain-target: include all modules for development Jonathan Liu
  -- strict thread matches above, loose matches on Subject: below --
2014-03-02  2:59 [meta-qt5][PATCH v2 1/2] qtimageformats: allow empty qtimageformats package Jonathan Liu

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=53129D76.9060802@gmail.com \
    --to=net147@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.