From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2 2/6] gettext: remove support for gettext-tools on target
Date: Sun, 8 Jun 2014 23:27:52 +0200 [thread overview]
Message-ID: <20140608212752.GS3266@free.fr> (raw)
In-Reply-To: <1401654214-19384-3-git-send-email-thomas.petazzoni@free-electrons.com>
Thomas, All,
On 2014-06-01 22:23 +0200, Thomas Petazzoni spake thusly:
> This commit removes the BR2_PACKAGE_GETTEXT_TOOLS option, which could
> be used to install gettext tools on the target. This is not needed,
> because Buildroot is not designed to provide a full development
> environment on the target, and gettext translation files should be
> processed on the build machine, using the host gettext tools.
>
> Remove this option will allow to optimize the build time of gettext on
> the target, by only building the gettext runtime libraries.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Tested-by: Andrew Ruder <andrew.ruder@elecsyscorp.com>
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Regards,
Yann E. MORIN.
> ---
> Config.in.legacy | 12 ++++++++++++
> package/gettext/Config.in | 14 --------------
> package/gettext/gettext.mk | 4 ----
> 3 files changed, 12 insertions(+), 18 deletions(-)
>
> diff --git a/Config.in.legacy b/Config.in.legacy
> index 00661db..50f7363 100644
> --- a/Config.in.legacy
> +++ b/Config.in.legacy
> @@ -99,6 +99,18 @@ comment "----------------------------------------------------"
> endif
>
> ###############################################################################
> +comment "Legacy options removed in 2014.08"
> +
> +config BR2_PACKAGE_GETTEXT_TOOLS
> + bool "support for gettext-tools on target has been removed"
> + select BR2_LEGACY
> + help
> + The option to install the gettext utilities on the target
> + has been removed. This is not necessary as Buildroot is not
> + designed to provide a full development environment on the
> + target. gettext tools should be used on the build machine
> + instead.
> +
> comment "Legacy options removed in 2014.05"
>
> config BR2_PACKAGE_EVTEST_CAPTURE
> diff --git a/package/gettext/Config.in b/package/gettext/Config.in
> index d33dd3a..158b14e 100644
> --- a/package/gettext/Config.in
> +++ b/package/gettext/Config.in
> @@ -13,20 +13,6 @@ config BR2_PACKAGE_GETTEXT
>
> http://www.gnu.org/software/gettext/
>
> -if BR2_PACKAGE_GETTEXT
> -
> -config BR2_PACKAGE_GETTEXT_TOOLS
> - bool "Install gettext tools"
> - depends on BR2_USE_MMU # fork()
> - depends on BR2_LARGEFILE
> - select BR2_PACKAGE_LIBICONV if !BR2_ENABLE_LOCALE
> - help
> - This option allows to install the complete gettext suite in
> - the target filesystem. This is typically not useful for
> - correct operation of programs.
> -
> -endif
> -
> comment "gettext needs a toolchain w/ wchar"
> depends on BR2_NEEDS_GETTEXT
> depends on !BR2_USE_WCHAR
> diff --git a/package/gettext/gettext.mk b/package/gettext/gettext.mk
> index b5efa76..52a72db 100644
> --- a/package/gettext/gettext.mk
> +++ b/package/gettext/gettext.mk
> @@ -46,16 +46,12 @@ ifeq ($(BR2_ENABLE_LOCALE),)
> GETTEXT_CONF_OPT += --enable-nls
> endif
>
> -# When the gettext tools are not enabled in the configuration, we only
> -# install libintl to the target.
> -ifeq ($(BR2_PACKAGE_GETTEXT_TOOLS),)
> # When static libs are preferred the .so files aren't created
> ifeq ($(BR2_PREFER_STATIC_LIB),)
> define GETTEXT_INSTALL_TARGET_CMDS
> cp -dpf $(STAGING_DIR)/usr/lib/libintl*.so* $(TARGET_DIR)/usr/lib/
> endef
> endif
> -endif # GETTEXT_TOOLS = n
>
> # Disable interactive confirmation in host gettextize for package fixups
> define HOST_GETTEXT_GETTEXTIZE_CONFIRMATION
> --
> 1.9.3
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-06-08 21:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-01 20:23 [Buildroot] [PATCHv2 0/6] gettext improvements Thomas Petazzoni
2014-06-01 20:23 ` [Buildroot] [PATCHv2 1/6] minidlna: do not select BR2_PACKAGE_GETTEXT_TOOLS Thomas Petazzoni
2014-06-02 20:29 ` Bernd Kuhls
2014-06-08 20:55 ` Yann E. MORIN
2014-06-01 20:23 ` [Buildroot] [PATCHv2 2/6] gettext: remove support for gettext-tools on target Thomas Petazzoni
2014-06-08 21:27 ` Yann E. MORIN [this message]
2014-06-01 20:23 ` [Buildroot] [PATCHv2 3/6] gettext: optimize build time Thomas Petazzoni
2014-06-08 22:26 ` Yann E. MORIN
2014-06-01 20:23 ` [Buildroot] [PATCHv2 4/6] gettext: allow building when BR2_NEEDS_GETTEXT is not selected Thomas Petazzoni
2014-06-01 20:23 ` [Buildroot] [PATCHv2 5/6] ecryptfs-utils: select gettext, needed for command line utilities Thomas Petazzoni
2014-06-01 20:23 ` [Buildroot] [PATCHv2 6/6] docs/manual: update documentation about gettext handling Thomas Petazzoni
2014-06-02 5:50 ` Thomas De Schampheleire
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=20140608212752.GS3266@free.fr \
--to=yann.morin.1998@free.fr \
--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