All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Hadjinlian <maxime.hadjinlian@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v7 4/4] xbmc: new package
Date: Wed, 19 Feb 2014 01:14:52 +0100	[thread overview]
Message-ID: <CAGduivzYVd3VFG3PDtPUJjLjtwaAMWydJbEZ6Yfyw6gwc4gLiA@mail.gmail.com> (raw)
In-Reply-To: <5303A6E3.8010209@barkynet.com>

Hi Martin, all
On Tue, Feb 18, 2014 at 7:30 PM, Martin Bark <martin@barkynet.com> wrote:
> Maxime, Thomas,
>
>
> On 18/02/14 17:02, Maxime Hadjinlian wrote:
>>
>> Hi Thomas, all
>> On Tue, Feb 18, 2014 at 5:38 PM, Thomas Petazzoni
>> <thomas.petazzoni@free-electrons.com> wrote:
>>>
>>> Dear Maxime Hadjinlian,
>>>
>>> On Tue, 18 Feb 2014 00:37:13 +0100, Maxime Hadjinlian wrote:
>>>
>>>> diff --git a/package/xbmc/Config.in b/package/xbmc/Config.in
>>>> new file mode 100644
>>>> index 0000000..23650ed
>>>> --- /dev/null
>>>> +++ b/package/xbmc/Config.in
>>>> @@ -0,0 +1,165 @@
>>>> +comment "xbmc requires an OpenGL-capable backend"
>>>> +     depends on !(BR2_PACKAGE_HAS_OPENGL_EGL &&
>>>> BR2_PACKAGE_HAS_OPENGL_ES)
>>>
>>>
>>> I would make the comment more specific:
>>>
>>> comment "xbmc requires an OpenGL ES and EGL backend"
>>>
>>>> +# External toolchain are required because of a missing bitdefs.h
>>>> +comment "xbmc needs an (e)glibc external toolchain w/ C++, wchar"
>>>> +     depends on !(BR2_TOOLCHAIN_USES_GLIBC && BR2_INSTALL_LIBSTDCPP &&
>>>> BR2_USE_WCHAR) || BR2_TOOLCHAIN_BUILDROOT
>>>
>>>
>>> This dependency does not make much sense to me. Your comment mentions
>>> "external toolchain", but it is not reflected by the dependencies.
>>> Moreover, we now have glibc/eglibc support in the internal backend, so
>>> I don't really see how there could be a difference between internal and
>>> external here. Additionally, if the C library is glibc or eglibc, then
>>> you are guaranteed to have wchar support. So if what you need is
>>> eglibc/glibc, then please do:
>>>
>>> comment "xbmc needs an (e)glibc toolchain w/ C++"
>>>          depends on !BR2_TOOLCHAIN_USES_GLIBC || !BR2_INSTALL_LIBSTDCPP
>>>
>> The problem I had with internal toolchain, {X}libc was that, the
>> bitdefs.h is missing, and XBMC needs it.
>> I'll look at it another time as maybe my tests were not thorough enough.
>>
>
> locally i tried this change and the following defconfig
>
> BR2_arm=y
> BR2_arm1176jzf_s=y
> BR2_TOOLCHAIN_BUILDROOT_GLIBC=y
> BR2_TOOLCHAIN_BUILDROOT_CXX=y
> BR2_PACKAGE_XBMC=y
> BR2_PACKAGE_RPI_USERLAND=y
>
> and it all built ok.  I also tried with eglibc and it build ok too.
>
> Thanks
That's really nice to know. I'll do some tests on my own. But it would
mean I could lift the restriction on using external toolchain to only
using one with glibc/eglibc, when Gotham is ready we could lift this
restriction altogether !
Thanks a lot for testing this !

  reply	other threads:[~2014-02-19  0:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-17 23:37 [Buildroot] [PATCH v7 0/4] Introducing XBMC Maxime Hadjinlian
2014-02-17 23:37 ` [Buildroot] [PATCH v7 1/4] sdl: add host version Maxime Hadjinlian
2014-02-18 16:13   ` Thomas Petazzoni
2014-02-18 16:41     ` Maxime Hadjinlian
2014-02-19 15:12   ` Peter Korsgaard
2014-02-17 23:37 ` [Buildroot] [PATCH v7 2/4] sdl_image: " Maxime Hadjinlian
2014-02-18 16:11   ` Thomas Petazzoni
2014-02-19 15:14     ` Peter Korsgaard
2014-02-19 15:14   ` Peter Korsgaard
2014-02-17 23:37 ` [Buildroot] [PATCH v7 3/4] infra: Introduce BR2_HOST_NEEDS_JAVA Maxime Hadjinlian
2014-02-18 16:18   ` Thomas Petazzoni
2014-02-18 16:41     ` Maxime Hadjinlian
2014-02-18 16:44       ` Thomas Petazzoni
2014-02-19 15:19   ` Peter Korsgaard
2014-02-17 23:37 ` [Buildroot] [PATCH v7 4/4] xbmc: new package Maxime Hadjinlian
2014-02-18 16:38   ` Thomas Petazzoni
2014-02-18 17:02     ` Maxime Hadjinlian
2014-02-18 18:30       ` Martin Bark
2014-02-19  0:14         ` Maxime Hadjinlian [this message]
2014-02-18 16:57 ` [Buildroot] [PATCH v7 0/4] Introducing XBMC Martin Bark
2014-02-18 17:03   ` Maxime Hadjinlian

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=CAGduivzYVd3VFG3PDtPUJjLjtwaAMWydJbEZ6Yfyw6gwc4gLiA@mail.gmail.com \
    --to=maxime.hadjinlian@gmail.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.