2bc3bca6d8
Until now, we thought that gettext was only needed for the target for uClibc toolchains, to provide the gettext functions that are normally provided directly by glibc. However, the gettext runtime actually does more than providing the equivalent of those C library functions: it also provides certain command line tools, like 'gettext' to get translated strings from the shell. This tool is for example used by certain ecryptfs-utils scripts to get translated strings. It is therefore necessary to be able to build the gettext package even for glibc toolchains. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
18 lines
512 B
Plaintext
18 lines
512 B
Plaintext
config BR2_PACKAGE_GETTEXT
|
|
bool "gettext"
|
|
depends on BR2_USE_WCHAR
|
|
help
|
|
The GNU `gettext' utilities are a set of tools that provide a
|
|
framework to help other GNU packages produce multi-lingual
|
|
messages.
|
|
|
|
Only the libintl library will be installed in the
|
|
target. The full gettext suite, including tools, will be
|
|
installed in the staging directory.
|
|
|
|
http://www.gnu.org/software/gettext/
|
|
|
|
comment "gettext needs a toolchain w/ wchar"
|
|
depends on BR2_NEEDS_GETTEXT
|
|
depends on !BR2_USE_WCHAR
|