From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Ncurses wide support
Date: Tue, 15 Oct 2013 08:56:30 -0300 [thread overview]
Message-ID: <525D2D6E.9000108@zacarias.com.ar> (raw)
In-Reply-To: <20131015133626.180de72d@skate>
On 10/15/2013 08:36 AM, Thomas Petazzoni wrote:
>> Maybe you could explain this in detail? Or draft some ncurses.mk
>> patch for me to take care of it?
>>
>> I know you probably don't care about nano, but it's currently broken
>> because of this ncursesw lack.
>
> Not sure to follow the original problem. If nano needs ncursesw, why
> don't you enable wchar support in your toolchain so that ncursesw gets
> built?
Because ncurses (upstream) just builds the narrow or wide versions, not
both. Currently we build only the narrow version no matter what.
And IIRC some packages don't expect the wide version even if the
toolchain is WCHAR.
Regards.
next prev parent reply other threads:[~2013-10-15 11:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 10:09 [Buildroot] Ncurses wide support Ezequiel García
2013-10-15 10:18 ` Gustavo Zacarias
2013-10-15 10:48 ` Ezequiel García
2013-10-15 11:36 ` Thomas Petazzoni
2013-10-15 11:56 ` Ezequiel García
2013-10-15 11:56 ` Gustavo Zacarias [this message]
2013-10-15 11:59 ` Thomas Petazzoni
2013-10-15 12:01 ` Ezequiel García
2013-10-15 12:02 ` Gustavo Zacarias
2013-10-15 12:04 ` Thomas Petazzoni
2013-10-15 12:51 ` 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=525D2D6E.9000108@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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