From: Jonathan Liu <net147@gmail.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-qt5][PATCH v4 2/2] packagegroup-qt5-toolchain-target: include all modules for development
Date: Tue, 11 Mar 2014 22:39:15 +1100 [thread overview]
Message-ID: <531EF5E3.2060509@gmail.com> (raw)
In-Reply-To: <CAP9ODKpaS0r9ZC7k3wN=oQ_4=j90DxR-LEwdBMCKrHDKmaWMHw@mail.gmail.com>
On 5/03/2014 1:34 AM, Otavio Salvador wrote:
> On Tue, Mar 4, 2014 at 12:43 AM, Jonathan Liu <net147@gmail.com> wrote:
>> On 4 March 2014 06:53, Otavio Salvador <otavio@ossystems.com.br> wrote:
>>> On Sun, Mar 2, 2014 at 1:22 AM, Jonathan Liu <net147@gmail.com> wrote:
>>>> This adds the necessary target packages for development with all of the
>>>> Qt 5 modules.
>>>>
>>>> Signed-off-by: Jonathan Liu <net147@gmail.com>
>>> Why are you adding qttools here? this is not need for toolchain use,
>>> is it? It is need for host.
>> The QtTools module includes components that may be used by
>> applications - http://qt-project.org/doc/qt-5/qtmodules.html#qt-tools
> From the doc it is not clear to me how it will be used in the target,
> it seems something used in host.
>
> Could you help me to understand your reasoning for it?
>
It includes Qt Help which is used to implement context-sensitive help to
the user in Qt applications.
Regards,
Jonathan
next prev parent reply other threads:[~2014-03-11 11:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-02 4:22 [meta-qt5][PATCH v4 1/2] qtimageformats: allow empty qtimageformats package Jonathan Liu
2014-03-02 4:22 ` [meta-qt5][PATCH v4 2/2] packagegroup-qt5-toolchain-target: include all modules for development Jonathan Liu
2014-03-03 19:53 ` Otavio Salvador
2014-03-04 3:43 ` Jonathan Liu
2014-03-04 14:34 ` Otavio Salvador
2014-03-11 11:39 ` Jonathan Liu [this message]
2014-03-12 18:42 ` Otavio Salvador
2014-03-12 21:03 ` Jonathan Liu
2014-03-12 22:37 ` Otavio Salvador
2014-03-12 22:47 ` Jonathan Liu
2014-03-04 20:00 ` Denys Dmytriyenko
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=531EF5E3.2060509@gmail.com \
--to=net147@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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