Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/gettext-tiny: Add new package
Date: Tue, 21 Aug 2018 17:29:13 +0200	[thread overview]
Message-ID: <20180821172913.1a7eb830@windsurf> (raw)
In-Reply-To: <87r2irvljb.fsf@tkos.co.il>

Baruch, Vadim,

On Tue, 21 Aug 2018 17:31:20 +0300, Baruch Siach wrote:

> > gettext-tiny provides lightweight replacements for tools typically used
> > from the GNU gettext suite, which is incredibly bloated and takes a lot
> > of time to build (in the order of an hour on slow devices). the most
> > notable component is msgfmt which is used to create binary translation
> > files in the .mo format out of textual input files in .po format. this
> > is the most important tool for building software from source, because it
> > is used from the build processes of many software packages.  
> 
> Thanks. gettext is indeed a huge CPU cycles drain.

Agreed, I was looking forward to someone taking over the task of
packaging gettext-tiny. So thanks Vadim for taking on this task!

However, packaging gettext-tiny requires a lot more than just creating
a package for it. Indeed, how do you select whether you want to use
gettext or gettext-tiny ? There should be some global knob that defines
that, and which affects the TARGET_NLS_DEPENDENCIES variable.

And then, there's the case of packages that need gettext even when NLS
support is disabled.

So: a big YES to adding gettext-tiny in Buildroot, but we want a proper
clean integration, not just a separate package. Vadim: you can read
https://buildroot.org/downloads/manual/manual.html#_gettext_integration_and_interaction_with_packages
to learn a bit about the current gettext integration in Buildroot.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2018-08-21 15:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-21 14:22 [Buildroot] [PATCH 1/1] package/gettext-tiny: Add new package Vadim Kochan
2018-08-21 14:31 ` Baruch Siach
     [not found]   ` <CACV=4zeWfsgbrQx4g2cmssEjtwvPj+a_9Fu5FzfSH4h_Q4fXdw@mail.gmail.com>
2018-08-21 14:44     ` Baruch Siach
2018-08-21 15:29   ` Thomas Petazzoni [this message]
2018-08-21 15:51     ` Vadim Kochan
2018-08-21 17:36       ` Thomas Petazzoni
2018-08-21 20:07         ` Vadim Kochan
2018-08-21 20:10           ` Thomas Petazzoni
2018-08-22  7:02             ` Vadim Kochan
2018-10-09 12:45 ` Thomas Petazzoni
2018-10-09 13:12   ` Vadim Kochan
2018-10-09 13:12     ` Thomas Petazzoni

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=20180821172913.1a7eb830@windsurf \
    --to=thomas.petazzoni@bootlin.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