From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] multchoice menu with kconfig
Date: Mon, 18 Feb 2013 18:16:08 +0200 [thread overview]
Message-ID: <512253C8.2050309@petroprogram.com> (raw)
In-Reply-To: <512251F3.7060101@mind.be>
18.2.2013 18:08, Arnout Vandecappelle kirjoitti:
> On 18/02/13 17:01, Stefan Fr?berg wrote:
>> And because this iso-codes package does not seem to have nothing but
>> punch .po files
>> and not link against anything then changing that ISO_CODES_DEPENDENCIES
>> to host-gettext should be good.
>
> Err... But iso-codes doesn't need host-gettext, does it? It probably
> doesn't make much sense without locale support in the toolchain, but
> otherwise I see no dependencies except python (which is already a
> buildroot dependency).
>
But don't you need at least host gettext stuff to process those .po files ?
I should now tell at this point that besides giving -lintl linker flags
and giving --disable-nls to configure scripts
I absolutely have no idea how gettext works. :D
Im confused now.
So no dependencies at all ????? Or gettext dependencies with locale
checking ?????? (Like Thomas said in his post)
Regards
Stefan
next prev parent reply other threads:[~2013-02-18 16:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 13:49 [Buildroot] multchoice menu with kconfig Stefan Fröberg
2013-02-18 15:33 ` Arnout Vandecappelle
2013-02-18 15:45 ` Stefan Fröberg
2013-02-18 15:58 ` Arnout Vandecappelle
2013-02-18 16:01 ` Stefan Fröberg
2013-02-18 16:08 ` Arnout Vandecappelle
2013-02-18 16:16 ` Stefan Fröberg [this message]
2013-02-18 16:23 ` Arnout Vandecappelle
2013-02-18 16:32 ` Stefan Fröberg
2013-02-18 21:36 ` [Buildroot] autopoint [was: Re: multchoice menu with kconfig] Arnout Vandecappelle
2013-02-18 22:03 ` Stefan Fröberg
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=512253C8.2050309@petroprogram.com \
--to=stefan.froberg@petroprogram.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