[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CDK/Ncurses Question (Problem)

From: Marc Smith
Subject: Re: CDK/Ncurses Question (Problem)
Date: Sat, 7 Dec 2013 19:24:28 -0500

Thanks for the quick reply; I found the problem... it was with libcdk -- ncurses5-config gives the default path to headers/library, and on some systems these actually existed so they were built against instead of the local ncurses install. I added the 'exec-prefix' and 'prefix' options and the application works correctly with the new libcdk.


On Sat, Dec 7, 2013 at 12:53 PM, Thomas Dickey <address@hidden> wrote:
On Sat, Dec 07, 2013 at 10:40:13AM -0500, Marc Smith wrote:
> Hi,
> I have an application that utilizes CDK, and this program is part of a
> larger project that is more like a Linux distribution. The problem is when
> its built on some hosts, the line drawing characters do not all display
> correctly, some corner characters are a caret (^) or a ^@ and the enter key
> does not function correctly.
> Here is a picture of the problem:
> http://longfellow.mcc.edu/~marc.smith/bad_screen.png
> Here is a picture of what it should look like:
> http://longfellow.mcc.edu/~marc.smith/normal_screen.png
> The TUI application itself, and all supporting libraries (ncurses, cdk) are
> built on the same host which is part of a large Makefile that builds and
> packages everything (the application and libraries).
> ncurses 5.7.20081102
> cdk 5.0-20120323
> I'm sure the issue comes from something during the build, but I'm just not
> sure where to start looking. Any ideas or tips would be greatly appreciated.

I'd start first by checking if the locale settings differ on the machines,
and if I'm running the same terminal emulator (and same terminal description).

If it's not that simple, I'd build a copy of ncurses with the trace feature
enabled, rebuild cdk using _that_ and collect a trace showing the
screen-updates for the program.

Thomas E. Dickey <address@hidden>

Version: GnuPG v1.4.10 (GNU/Linux)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]