From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v6] toolchain: add option to copy the gconv libraries
Date: Mon, 28 Jul 2014 20:50:17 +0200 [thread overview]
Message-ID: <20140728205017.540a2ce6@free-electrons.com> (raw)
In-Reply-To: <1406489312-32491-1-git-send-email-yann.morin.1998@free.fr>
Dear Yann E. MORIN,
On Sun, 27 Jul 2014 21:28:32 +0200, Yann E. MORIN wrote:
> The gconv libraries are used to translate between different character sets
> ('charsets', even 'csets' sometimes). Some packages need them to present
> text to the user (eg. XBMC Gotham).
>
> In (e)glibc they are implemented by the internal implemenation of iconv,
> called gconv, and are provided as dlopen-able libraries.
>
> Note that some gconv modules need extra libraries (shared by more than
> one gconv module), so we must, when adding a subset of modules, scan the
> installed modules in search of the missing libraries.
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Maxime Hadjinlian <maxime.hadjinlian@gmail.com>
> Cc: Bernd Kuhls <bernd.kuhls@t-online.de>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> Cc: Eric Limpens <limpens@gmail.com>
Thanks, I've applied this version of the patch. I fixed the coding
style in the expunge-gconv-modules script, to make it match a more
normal coding style (i.e no space after opening parenthesis and before
closing parenthesis, space before/after operators, etc.).
Also, on the design principle, there are two things that will have to
fixed as followup patches:
1/ The fact that the new options appear in the Toolchain menu. It's
already a problem with the locale-related settings. I believe they
are more "System setting" than "Toolchain settings".
2/ The copy of the gconv modules should not be done as a target
finalize hook (contrary to what I suggested earlier), but should
actually be integrated as part of the package/glibc and
toolchain/toolchain-external logic, so that those gconv modules are
considered to be part of the toolchain (from a build/install time
point of view, and also from a package size point of view in
relation with my script graphing per-package size). There is no
reason to have this installation as a target-finalize hook.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-07-28 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-27 19:28 [Buildroot] [PATCH v6] toolchain: add option to copy the gconv libraries Yann E. MORIN
2014-07-28 18:06 ` Eric Limpens
2014-07-28 18:50 ` 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=20140728205017.540a2ce6@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