On 5/19/2010 2:04 AM, rushojp wrote:
> u...@localhost /usr/include
> $ for h in curses.h eti.h form.h menu.h ncurses.h panel.h term.h unctrl.h ; do
>> ln -s ncurses/$h $h ;done
>
> I think libncurses-devel package should have these symlink files.
Is anybody going to read the documentation? From
/
u...@localhost /usr/include
$ for h in curses.h eti.h form.h menu.h ncurses.h panel.h term.h unctrl.h ; do
> ln -s ncurses/$h $h ;done
I think libncurses-devel package should have these symlink files.
http://www.rpmseek.com/rpm-pl/libncurses-devel.html?hl=com&cs=libncurses-devel:PN:0:0:0:0:0
20
Steven Collins wrote:
Perhaps the examples are assuming you are controlling the include path
via a -I switch to the compiler, thus avoiding any direct reference in
the source code that would imply knowledge of your installation?
In older ncurses versions, ncurses.h was in /usr/include.
But now
Perhaps the examples are assuming you are controlling the include path
via a -I switch to the compiler, thus avoiding any direct reference in
the source code that would imply knowledge of your installation?
gcc -I /usr/include/ncurses ...
On Mon, May 17, 2010 at 12:06, Luis Vital <> wrote:
> Hi,
On 17/05/2010 19:06, Luis Vital wrote:
> I just installed NCurses under Cygwin.
> Looking at the file list after the instalation I see that I have:
>
> /usr/include/curses.h
> /usr/include/ncurses.h
> etc.
The real question is how these got there. They aren't part of any Cygwin
package. They
Hi,
I just installed NCurses under Cygwin.
Looking at the file list after the instalation I see that I have:
/usr/include/curses.h
/usr/include/ncurses.h
etc.
and
/usr/include/ncurses/curses.h
/usr/include/ncurses/ncurses.h
etc.
If I compile using #include I got errors but if I
compile using
6 matches
Mail list logo
