From: Khem Raj <raj.khem@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/5] taglib: Update to 1.11.1
Date: Mon, 21 Nov 2016 19:46:21 -0800 [thread overview]
Message-ID: <eb6aeb51-c0c5-fe39-f3e1-ac1dfede129b@gmail.com> (raw)
In-Reply-To: <CAJTo0Laq+KdjYoNvTM3DV+X8aGGdfWyJM=1z830=8T1orbqaJQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 695 bytes --]
On 11/21/16 9:57 AM, Burton, Ross wrote:
> On 16 November 2016 at 17:47, Khem Raj <raj.khem@gmail.com
> <mailto:raj.khem@gmail.com>> wrote:
>
> -DEPENDS = "zlib"
> +DEPENDS = "zlib boost"
>
>
> This appears to be an optional dependency and pulls in all of boost for a byte
> swapping macro, which whilst I appreciate is in the spirit of C++ isn't great
> considering GCC has its own macros that it also checks for.
>
> Can we just fix the tests so they don't error if boost isn't present and force
> it to off?
its a build time dependency. Do we have a usecase/images where taglib is used
and boost is just pulled into build because of taglib ?
>
> Ross
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 211 bytes --]
next prev parent reply other threads:[~2016-11-22 3:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 17:47 [PATCH 1/5] systemd: Upgrade to 232 Khem Raj
2016-11-16 17:47 ` [PATCH 2/5] taglib: Update to 1.11.1 Khem Raj
2016-11-21 17:57 ` Burton, Ross
2016-11-22 3:46 ` Khem Raj [this message]
2016-11-22 10:44 ` Burton, Ross
2016-11-22 11:20 ` Burton, Ross
2016-11-22 16:34 ` Khem Raj
2016-11-16 17:47 ` [PATCH 3/5] musl: Update to latest on master Khem Raj
2016-11-16 17:47 ` [PATCH 4/5] cmake.bbclass: Set CXXFLAGS and CFLAGS Khem Raj
2016-11-16 17:47 ` [PATCH 5/5] binutils: Fix parsing of ppc apuinfo for spe Khem Raj
2016-11-18 12:38 ` [PATCH 1/5] systemd: Upgrade to 232 Burton, Ross
2016-11-18 17:35 ` Khem Raj
2016-11-22 3:51 ` Khem Raj
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=eb6aeb51-c0c5-fe39-f3e1-ac1dfede129b@gmail.com \
--to=raj.khem@gmail.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