Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] avahi: link with libintl if libglib2 is enabled
Date: Wed, 19 Oct 2016 21:57:35 +0200	[thread overview]
Message-ID: <20161019215735.52749cd8@free-electrons.com> (raw)
In-Reply-To: <20161019172550.GV21808@waldemar-brodkorb.de>

Hello,

On Wed, 19 Oct 2016 19:25:50 +0200, Waldemar Brodkorb wrote:

> Just want to mention that I want integrate gettext-tiny into
> uClibc-ng soon. It is a stub implementation. The existing stub isn't
> selectable since a while...
> 
> https://github.com/rofl0r/gettext-tiny

Interesting. I once started experimenting a bit with integrating
gettext-tiny in Buildroot, but it was not that easy to achieve.

In fact, the problem with gettext is two-fold: it's both the target
gettext (i.e libintl) but also the host gettext (for gettext tools)
that are annoyingly long to build.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-10-19 19:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-18 14:53 [Buildroot] [PATCH 1/1] avahi: link with libintl if libglib2 is enabled Johan Oudinet
2016-10-18 15:25 ` Thomas Petazzoni
2016-10-19 12:42   ` Johan Oudinet
2016-10-19 12:59     ` Thomas Petazzoni
2016-10-19 16:23       ` Johan Oudinet
2016-10-19 16:27         ` Arnout Vandecappelle
2016-10-19 17:25           ` Waldemar Brodkorb
2016-10-19 19:57             ` Thomas Petazzoni [this message]
2016-10-19 19:55           ` Thomas Petazzoni
2016-10-20  8:25             ` Arnout Vandecappelle
2017-06-10 19:32 ` Bernd Kuhls

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=20161019215735.52749cd8@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