From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/libasplib: bump version
Date: Wed, 25 Jan 2017 16:44:58 +1300 [thread overview]
Message-ID: <20170125164458.5a4043e1@free-electrons.com> (raw)
In-Reply-To: <20170101120244.13383-1-bernd.kuhls@t-online.de>
Hello,
On Sun, 1 Jan 2017 13:02:43 +0100, Bernd Kuhls wrote:
> libasplib now contains modules, we enable only those for the moment
> which do not need external dependencies. We are not in a hurry to fully
> support all features of this package because the upcoming Kodi release
> 17.x-Krypton will not carry any ADSP add-ons:
> https://github.com/xbmc/repo-binary-addons/commit/db3b767309df25daae4f01f01dba85ca7b3464b0
>
> -DASPLIB_MODULES_TO_BUILD=some looks hackish because the default is to
> enable all modules:
> https://github.com/AchimTuran/asplib/blob/master/CMakeLists.txt#L35
>
> But -DASPLIB_MODULES_TO_BUILD=OFF does not disable the build of all
> modules as well because of
> https://github.com/AchimTuran/asplib/blob/master/asplib_modules/CMakeLists.txt#L19
> so I added "some" as fake value.
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/libasplib/libasplib.hash | 2 +-
> package/libasplib/libasplib.mk | 10 +++++++++-
> 2 files changed, 10 insertions(+), 2 deletions(-)
Both patches applied. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-01-25 3:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-01 12:02 [Buildroot] [PATCH 1/2] package/libasplib: bump version Bernd Kuhls
2017-01-01 12:02 ` [Buildroot] [PATCH 2/2] package/libasplib: fix build error on m68k Bernd Kuhls
2017-01-25 3:44 ` 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=20170125164458.5a4043e1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox