All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/boost: boost-filesystem needs wchar
Date: Thu, 23 Jul 2015 09:31:09 +0200	[thread overview]
Message-ID: <20150723093109.38aa581e@free-electrons.com> (raw)
In-Reply-To: <1437635893.2784.4.camel@embedded.rocks>

Dear J?rg Krause,

On Thu, 23 Jul 2015 09:18:13 +0200, J?rg Krause wrote:

> There are a lot more then five boost modules needing wchar. If we make
> boost depending on wchar we add reverse dependencies to some packages
> which could be build without wchar before.
> 
> What do you think?

 * cc-tool -> already depends on wchar
 * gnuradio -> already depends on wchar
 * kodi -> already depends on wchar
 * libftdi1 -> does not depend on wchar yet, but only the C++ bindings
   of libftdi1 need boost, so I think it's OK
 * mpd -> already depends on wchar
 * pulseview -> already depends on wchar
 * python-libconfig -> already depends on wchar since it depends on
   python or python3, and both depend on wchar
 * thrift -> already depends on wchar
 * yaml-cpp -> would add a wchar dependency
 * zmpqq -> already depends on wchar

So the only affected packages are the C++ bindings of libftdi1 and
yaml-cpp.

Conclusion: I believe it's reasonable to add a wchar dependency
globally to boost. It's a pain to keep track which sub-option of boost
needs or does not need wchar, and boost is a "big" thing, so having an
additional toolchain dependency that is nevertheless already very
common, is not a big issue.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2015-07-23  7:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-17 14:15 [Buildroot] [PATCH 1/1] package/boost: boost-filesystem needs wchar Jörg Krause
2015-07-18 12:13 ` Thomas Petazzoni
2015-07-22  6:55 ` Thomas Petazzoni
2015-07-23  6:08   ` Jörg Krause
2015-07-23  7:18   ` Jörg Krause
2015-07-23  7:31     ` Thomas Petazzoni [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=20150723093109.38aa581e@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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.