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 22:10:26 +0200 [thread overview]
Message-ID: <20180821221026.4fec5cf2@windsurf> (raw)
In-Reply-To: <CAMw6YJLASMAVyjqKs26zzzpxdpHV5ezQhaXu=nNyO3UwnQF-Yw@mail.gmail.com>
Hello Vadim,
On Tue, 21 Aug 2018 23:07:59 +0300, Vadim Kochan wrote:
> > - There are a few packages that unconditionally need host-gettext. Is
> > this really true ?
> Not sure about this)
In this situation, we have:
- aumix
- host-guile
- host-intltool (perhaps legit ?)
- host-libglib2
- libv4l (for AM_ICONV m4 macro)
- linphone
- mediastreamer
- host-mono
- sysstat (which also uses TARGET_NLS_DEPENDENCIES... weird)
- tvheadend
- host-wine
- xkeyboard-config
- zbar (for AM_ICONV m4 macro)
> > - Some packages need host-gettext because of the AM_ICONV m4 macro
> > provided by gettext.m4. Is gettext-tiny also providing the
> > gettext-related m4 macros ?
> Yes it has some set of m4 macrosses, but it needs to be tested how it
> works for the buildroot.
>
> What if I will start from converting gettext package into the virtual
> one (with renaming the original
> gettext -> gettext-gnu) ? And after I will try to add gettext-tiny as
> gettext provider.
Looks OK to me. I think the choice between gettext and gettext-tiny is
really a top-level decision, so it probably belongs near the "Enable
Native Language Support (NLS)" option in "System configuration".
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-21 20:10 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
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 [this message]
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=20180821221026.4fec5cf2@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