All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio.salvador@ossystems.com.br>
To: OpenEmbedded Devel List <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-qt5][PATCH] nativesdk-qtbase: use runtime linked dbus
Date: Tue, 16 Feb 2016 09:38:54 -0200	[thread overview]
Message-ID: <CAP9ODKqw8CKiXfdkbpXXonKO52ap8Cw9u2zsd_+x=57s0_CAWg@mail.gmail.com> (raw)
In-Reply-To: <56C2E83A.6080908@theqtcompany.com>

On Tue, Feb 16, 2016 at 7:13 AM, Samuli Piippo
<samuli.piippo@theqtcompany.com> wrote:
> On 16.02.2016 00:34, Otavio Salvador wrote:
>>
>> On Sun, Feb 14, 2016 at 2:25 PM, Samuli Piippo
>> <samuli.piippo@theqtcompany.com> wrote:
>>>
>>> Remove direct dependency to nativesdk-dbus. Instead configure
>>> qtbase to use runtime linked dbus library, if that is found.
>>>
>>> Signed-off-by: Samuli Piippo <samuli.piippo@theqtcompany.com>
>>
>>
>> Why? This puts a dependency on the host operating system version.
>>
>> Am I missing something?
>>
>
> Currently nativesdk-qtbase does not package libQt5DBus.so, so there nothing
> in the SDK that actual uses dbus, but it's still built as a dependency.
> If "qt5: add Qml support to lupdate" patch is merged, then nativesdk-dbus
> would be pulled into SDK as well, although I think it's still unlikely that
> anyone would need it. If there is really need for it, then you can always
> add nativesdk-dbus to your toolchain.

So why not remove libQt5Dbus.so at all, from the nativesdk?

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750


  reply	other threads:[~2016-02-16 11:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-14 16:25 [meta-qt5][PATCH] nativesdk-qtbase: use runtime linked dbus Samuli Piippo
2016-02-15 22:34 ` Otavio Salvador
2016-02-16  9:13   ` Samuli Piippo
2016-02-16 11:38     ` Otavio Salvador [this message]
2016-02-16 14:13       ` Samuli Piippo
2016-02-16 16:01         ` Otavio Salvador

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='CAP9ODKqw8CKiXfdkbpXXonKO52ap8Cw9u2zsd_+x=57s0_CAWg@mail.gmail.com' \
    --to=otavio.salvador@ossystems.com.br \
    --cc=openembedded-devel@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.