Define XCURSES if not DOS, OS2 or WIN32.

This commit is contained in:
William McBrine
2006-02-13 19:44:37 +00:00
parent f7dda123da
commit dc333a8eba
2 changed files with 15 additions and 4 deletions

View File

@@ -16,7 +16,7 @@
* See the file maintain.er for details of the current maintainer.
**************************************************************************/
/* $Id: curses.h,v 1.124 2006/02/08 17:57:18 wmcbrine Exp $ */
/* $Id: curses.h,v 1.125 2006/02/13 19:44:37 wmcbrine Exp $ */
/* ----------------------------------------------------------------------
PDCurses
@@ -372,6 +372,14 @@ PDCurses portable platform definitions list:
# include <os2.h>
#endif
/* If it's not DOS, or OS/2, or Windows, it must be XCurses */
#if !defined(DOS) && !defined(OS2) && !defined(WIN32)
# ifndef XCURSES
# define XCURSES
# endif
#endif
#include <stdarg.h>
#include <stdio.h> /* Required by X/Open usage below */

View File

@@ -8,9 +8,9 @@ between the curses program and the child process created to manage the X
stuff. XCurses also uses sockets for communication between the
processes.
When compiling your curses application, you need to add -DXCURSES, and
include the <curses.h> or <xcurses.h> that comes with XCurses. You also
need to link your code with the XCurses library.
When compiling your curses application, you need to include the
<curses.h> or <xcurses.h> that comes with XCurses. You also need to link
your code with the XCurses library.
XCurses programs use the X Toolkit Intrinsics libraries. You will need
to link your code with the following libraries under X11R5:
@@ -313,4 +313,7 @@ The XCursesExit() function is now called automatically via atexit().
(Multiple calls to it are OK, so you don't need to remove it if you've
already added it for previous versions of XCurses.)
It is no longer necessary to explicitly define XCURSES, except if
building under Cygwin. (It's defined automatically.)
**man-end**********************************************************************/