code.delx.au - gnu-emacs/blob - src/s/template.h

   1 /* Template for system description header files.
   2    This file describes the parameters that system description files
   3    should define or not.
   4    Copyright (C) 1985, 1986, 1992, 1999, 2001, 2002, 2003, 2004, 2005,
   5                  2006, 2007, 2008, 2009, 2010  Free Software Foundation, Inc.
   6
   7 This file is part of GNU Emacs.
   8
   9 GNU Emacs is free software: you can redistribute it and/or modify
  10 it under the terms of the GNU General Public License as published by
  11 the Free Software Foundation, either version 3 of the License, or
  12 (at your option) any later version.
  13
  14 GNU Emacs is distributed in the hope that it will be useful,
  15 but WITHOUT ANY WARRANTY; without even the implied warranty of
  16 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  17 GNU General Public License for more details.
  18
  19 You should have received a copy of the GNU General Public License
  20 along with GNU Emacs.  If not, see <http://www.gnu.org/licenses/>.  */
  21
  22
  23 /*
  24  *      Define symbols to identify the version of Unix this is.
  25  *      Define all the symbols that apply correctly.
  26  */
  27
  28 /* #define USG5 */
  29 /* #define USG */
  30 /* #define HPUX */
  31 /* #define BSD4_2 */
  32 /* #define BSD4_3 */
  33 /* #define BSD_SYSTEM */
  34
  35 /* SYSTEM_TYPE should indicate the kind of system you are using.
  36  It sets the Lisp variable system-type.  */
  37
  38 #define SYSTEM_TYPE "berkeley-unix"
  39
  40 /* Emacs can read input using SIGIO and buffering characters itself,
  41    or using CBREAK mode and making C-g cause SIGINT.
  42    The choice is controlled by the variable interrupt_input.
  43
  44    Define INTERRUPT_INPUT to make interrupt_input = 1 the default (use SIGIO)
  45
  46    Emacs uses the presence or absence of the SIGIO and BROKEN_SIGIO macros
  47    to indicate whether or not signal-driven I/O is possible.  It uses
  48    INTERRUPT_INPUT to decide whether to use it by default.
  49
  50    SIGIO can be used only on systems that implement it (4.2 and 4.3).
  51    CBREAK mode has two disadvantages
  52      1) At least in 4.2, it is impossible to handle the Meta key properly.
  53         I hear that in system V this problem does not exist.
  54      2) Control-G causes output to be discarded.
  55         I do not know whether this can be fixed in system V.
  56
  57    Another method of doing input is planned but not implemented.
  58    It would have Emacs fork off a separate process
  59    to read the input and send it to the true Emacs process
  60    through a pipe. */
  61
  62 #define INTERRUPT_INPUT
  63
  64 /* Letter to use in finding device name of first pty,
  65   if system supports pty's.  'a' means it is /dev/ptya0  */
  66
  67 #define FIRST_PTY_LETTER 'a'
  68
  69 /*
  70  *      Define HAVE_TERMIOS if the system provides POSIX-style
  71  *      functions and macros for terminal control.
  72  *
  73  *      Define HAVE_TERMIO if the system provides sysV-style ioctls
  74  *      for terminal control.
  75  *
  76  *      Do not define both.  HAVE_TERMIOS is preferred, if it is
  77  *      supported on your system.
  78  */
  79
  80 #define HAVE_TERMIOS
  81 /* #define HAVE_TERMIO */
  82
  83 /*
  84  *      Define HAVE_PTYS if the system supports pty devices.
  85  */
  86
  87 #define HAVE_PTYS
  88
  89 /* Define this symbol if your system has the functions bcopy, etc. */
  90
  91 #define BSTRING
  92
  93 /* subprocesses should be undefined if you do NOT want to
  94    have code for asynchronous subprocesses
  95    (as used in M-x compile and M-x shell).
  96    Currently only MSDOS does not support this. */
  97
  98 /* #undef subprocesses */
  99
 100 /* If your system uses COFF (Common Object File Format) then define the
 101    preprocessor symbol "COFF". */
 102
 103 /* #define COFF */
 104
 105 /* define MAIL_USE_FLOCK if the mailer uses flock
 106    to interlock access to /usr/spool/mail/$USER.
 107    The alternative is that a lock file named
 108    /usr/spool/mail/$USER.lock.  */
 109
 110 #define MAIL_USE_FLOCK
 111
 112 /* Define CLASH_DETECTION if you want lock files to be written
 113    so that Emacs can tell instantly when you try to modify
 114    a file that someone else has modified in his Emacs.  */
 115
 116 #define CLASH_DETECTION
 117
 118 /* Define this if your operating system declares signal handlers to
 119    have a type other than the usual.  `The usual' is `void' for ANSI C
 120    systems (i.e. when the __STDC__ macro is defined), and `int' for
 121    pre-ANSI systems.  If you're using GCC on an older system, __STDC__
 122    will be defined, but the system's include files will still say that
 123    signal returns int or whatever; in situations like that, define
 124    this to be what the system's include files want.  */
 125 /* #define SIGTYPE int */
 126
 127 /* If the character used to separate elements of the executable path
 128    is not ':', #define this to be the appropriate character constant.  */
 129 /* #define SEPCHAR ':' */
 130
 131 /* Define this if the system can use mmap for buffer text allocation.  */
 132 /* #define USE_MMAP_FOR_BUFFERS 1 */
 133
 134 /* ============================================================ */
 135
 136 /* Here, add any special hacks needed
 137    to make Emacs work on this system.  For example,
 138    you might define certain system call names that don't
 139    exist on your system, or that do different things on
 140    your system and must be used only through an encapsulation
 141    (Which you should place, by convention, in sysdep.c).  */
 142
 143 /* If the system's imake configuration file defines `NeedWidePrototypes'
 144    as `NO', we must define NARROWPROTO manually.  Such a define is
 145    generated in the Makefile generated by `xmkmf'.  If we don't
 146    define NARROWPROTO, we will see the wrong function prototypes
 147    for X functions taking float or double parameters.  */
 148
 149 /*  #define NARROWPROTO 1 */
 150
 151 /* ============================================================ */
 152
 153 /* After adding support for a new system, modify the large case
 154    statement in the `configure' script to recognize reasonable
 155    configuration names, and add a description of the system to
 156    `etc/MACHINES'.
 157
 158    If you've just fixed a problem in an existing configuration file,
 159    you should also check `etc/MACHINES' to make sure its descriptions
 160    of known problems in that configuration should be updated.  */
 161
 162 /* arch-tag: 4b426b11-cb2e-4c0e-a488-e663f76a0515
 163    (do not change this comment) */