All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Ncurses wide support
Date: Tue, 15 Oct 2013 07:18:59 -0300	[thread overview]
Message-ID: <525D1693.3010509@zacarias.com.ar> (raw)
In-Reply-To: <CAAEAJfCkpC6-ZnpcxYCgTiZN8=QJNY+wZg83Jjyzs8-e7jPkkw@mail.gmail.com>

On 10/15/2013 07:09 AM, Ezequiel Garc?a wrote:

> Currently Buildroot support building the non-wide (non-unicode) ncurses library.
> 
> While ncurses support an easy way to enable wide support with a configure option
> (--enable-widec), this option builds *only* the wide-enabled library
> (aka libncursesw)
> and not the vanilla one.
> 
> In other words, it's not possible to build both at the same time.
> 
> By looking at my Gentoo ebuild -which is also source based- it seems
> they solve this by
> simply building ncurses twice: first the vanilla, and then (if unicode
> is enabled) the
> wide-enabled one.
> 
> Questions that arise:
> 
> 1. Does Buildroot support something like this?

Hi.
There are tricks that could work, for instance by tweaking build and
install cmds you could build and stash the widec version in some new
directory inside the build one, then build the narrow version and
install both - being in another new directory makes it "make clean" safe.

> 2. Should we patch ncurses configure to change this behavior?
> (not really a fun solution, given this is an upstream choice)

Ehh no, probably not.

> 3. Do we even care?

It could be useful for people who want to edit multilanguage stuff in
the target nicely.
Personally i just copy the stuff over from my laptop, there's no
replacement for full vim syntax and rules :)
Regards.

  reply	other threads:[~2013-10-15 10:18 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 [this message]
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
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=525D1693.3010509@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.