Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Maxin B. John" <maxin.john@intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] libical: update to 2.0.0
Date: Thu, 28 Jan 2016 15:32:19 +0200	[thread overview]
Message-ID: <20160128133218.GC1902@mbabyjoh-mobl.fi.intel.com> (raw)
In-Reply-To: <CAJTo0LYFHTzv3vF0fz3VQ2sLFgBVfqKw4HO15cUJanCt76REbw@mail.gmail.com>

Hi,

On Thu, Jan 28, 2016 at 01:13:05PM +0000, Burton, Ross wrote:
>On 28 January 2016 at 13:13, Maxin B. John <maxin.john@intel.com> wrote:
>
>    These library dependencies do get detected automatically. This line can be removed
>        if we don't want to explicitly mention the dependencies.
>
>        We only need to mention library dependencies explicitly if they're opened at runtime and the dependency magic can't see them.  Please send a v2 for this patch.
>        Presumably although the ABI changed, the API is the same so bluez5 and so on still builds against libical 2?

Thanks for explaining that (bit carried away by the buildhistory-diff tool output). 
Sure, will send a v2 soon.

Yes, bluez5 build works fine with the libical 2.

> Ross

Best Regards,
Maxin


      parent reply	other threads:[~2016-01-28 13:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28 12:37 [PATCH 1/2] libical: update to 2.0.0 Maxin B. John
2016-01-28 12:37 ` [PATCH 2/2] connman: fix crash with iptables 1.6 Maxin B. John
2016-01-28 13:00 ` [PATCH 1/2] libical: update to 2.0.0 Burton, Ross
2016-01-28 13:13   ` Maxin B. John
2016-01-28 13:13     ` Burton, Ross
2016-01-28 13:15       ` Alexander Kanavin
2016-01-28 13:39         ` Maxin B. John
2016-01-28 13:40           ` Alexander Kanavin
2016-01-28 14:28             ` Burton, Ross
2016-01-28 13:32       ` Maxin B. John [this message]

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=20160128133218.GC1902@mbabyjoh-mobl.fi.intel.com \
    --to=maxin.john@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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