Yann E. MORIN" 8939bb3cff configure: fixup extended colors in wide-char-enabled ncurses
As Krzysztof puts it in its commit log in the Linux kernel:

    The ncurses library allows for extended colors. The support for extended
    colors support depends on wide-character support. ncurses headers
    enable extended colors (NCURSES_EXT_COLORS) only when wide-character
    support is enabled (NCURSES_WIDECHAR).

    The "make menuconfig" uses wide-character ncursesw library, which can be
    compiled with wide-character support, but does not define NCURSES_WIDECHAR
    and it's using headers without wide-character (and extended colors) support.

    This fixes problems with colors on systems with enabled extended colors
    (like PLD Linux). Without this patch "make menuconfig" is hard to use.

In kconfig-frontends, we fix this by adding the appropriate CPPFLAGS to the
mconf-specific ncurses CPPFLAGS.

Reported-by: Krzysztof Mazur <krzysiek@podlesie.net>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
2013-03-05 00:29:51 +01:00
2013-03-04 23:32:54 +01:00
2013-03-04 23:32:54 +01:00
2013-03-04 23:32:54 +01:00
2013-03-04 23:32:54 +01:00
2012-01-20 22:29:46 +01:00
2012-01-21 17:01:36 +01:00
2012-01-20 22:29:46 +01:00
2012-05-30 00:12:01 +02:00

This package contains the kconfig frontends and parser.

Kconfig is the configuration language used by the Linux kernel. This package
is a simple copy of the frontends and the parser found in the Linux kernel
source tree, with very minor changes to adapt them to being built out of
the kernel build infrastructure.

This package does *not* take any change to the parser or frontends. Such
changes shall be directed directly to the appropriate mailing list, and they
will eventually find their way is this package at the next sync:
    mailto:linux-kbuild@vger.kernel.org

However, if there is a bug in the packaging infrastructure, patches are
most welcome, of course! Most notably, because this is my very first
autostuff-based package, I may have done mistakes here and there...

As such, there are currently a few known limitations:

- statically linking is much, much more complex than it should be. I have
  been seemingly able to build part of the frontends with such incantations
  of ./configure and make:
    ./configure LDFLAGS=-static nconf_EXTRA_LIBS=-lgpm  \
                --disable-shared --enable-static        \
                --disable-gconf --disable-qconf
    make LDFLAGS="-all-static -static-libtool-libs"

- the nconf frontends requires (at least on my machine) to be linked against
  GPM; this is not detected when staticaly linking (hence the nconf_EXTRA_LIBS
  in the command above).

- statically linking the graphical frontends (gconf and qconf) is *not*
  supported: I am missing static libs for Qt3Support, so qconf does not link.
  And there is a stupid bug in libtool that prevents properly linking against
  installed static libraries (seemingly fixed in 2.4, but not quite yet, in
  fact...), so gconf does not link. That's why they are disabled above.

Note that, provided you have the required dependencies, all frontends are
properly built if you link dynamicaly. The following just works as expected:
    ./configure && make
Description
No description provided
Readme 690 KiB
Languages
C 74.4%
C++ 11.9%
M4 3.7%
Yacc 3.6%
Shell 2.5%
Other 3.9%