Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Building Kodi; dependencies
Date: Sun, 25 Feb 2018 17:23:34 +0100	[thread overview]
Message-ID: <20180225172334.131f0b72@windsurf.home> (raw)
In-Reply-To: <CAPzckP6rcjcRLvdCfPYr5bFUv6JVg6PShaxzq0yirmR41_T3XQ@mail.gmail.com>

Hello,

On Sun, 25 Feb 2018 11:59:05 +0100, Sjoerd Venema wrote:

> Coming from:
> 
> comment "kodi needs python w/ .py modules, a uClibc or glibc toolchain w/
> C++, threads, wchar, dynamic library, gcc >= 4.8, host gcc >= 4.6"
> depends on BR2_PACKAGE_KODI_ARCH_SUPPORTS
> depends on !BR2_INSTALL_LIBSTDCPP || !BR2_TOOLCHAIN_HAS_THREADS\
> || !BR2_USE_WCHAR || BR2_STATIC_LIBS \
> || !BR2_HOST_GCC_AT_LEAST_4_6 \
> || !BR2_TOOLCHAIN_GCC_AT_LEAST_4_8 \
> || BR2_TOOLCHAIN_USES_MUSL \
> || !BR2_PACKAGE_PYTHON \
> || BR2_PACKAGE_PYTHON_PYC_ONLY
> 
> First off, I assume the ! means a Not, so, for example  !BR2_USE_WCHAR
> means that BR2_USE_WCHAR must be [=n]. Correct?

You are looking at the dependencies of the comment, not the
dependencies of the option. So they are inverted.

For Kodi to build, wchar support must be available in the toolchain,
i.e BR2_USE_WCHAR must be 'y'. Therefore BR2_PACKAGE_KODI has a
"depends on BR2_USE_WCHAR"

Due to this dependency, the "kodi" option is not visible to the user
when wchar support is not enabled. In an attempt to help the user, in
such a situation we show the comment that you have seen. And therefore,
this comment is shown when one of the dependencies missing. Hence is
has a "depends on !BR2_USE_WCHAR" so that the comment appears when
wchar is *NOT* available.

Summary: enable BR2_USE_WCHAR.

> Secondly, can I set all these dependencies via make menuconfig? Or do I
> have to configure things outside of that environment?

Everything must be configured from inside menuconfig (unless you really
know what you're doing, in which case you can manually edit the .config
file).

> Now, a "catch 22" seems to be for example: BR2_TOOLCHAIN_HAS_THREADS (must
> be false)

No, BR2_TOOLCHAIN_HAS_THREADS must be true. See above my explanation
about the comment.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com

      parent reply	other threads:[~2018-02-25 16:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-25 10:59 [Buildroot] Building Kodi; dependencies Sjoerd Venema
2018-02-25 15:01 ` Bernd Kuhls
2018-02-25 16:17   ` Sjoerd Venema
2018-02-25 16:23 ` 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=20180225172334.131f0b72@windsurf.home \
    --to=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox