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
   5 Copyright (C) 1985-1986, 1992, 1999, 2001-2012  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 /* subprocesses should be undefined if you do NOT want to
  23    have code for asynchronous subprocesses
  24    (as used in M-x compile and M-x shell).
  25    Currently only MSDOS does not support this.  */
  26
  27 /* #undef subprocesses */
  28
  29 /* If the character used to separate elements of the executable path
  30    is not ':', #define this to be the appropriate character constant.  */
  31 /* #define SEPCHAR ':' */
  32
  33 /* ============================================================ */
  34
  35 /* Here, add any special hacks needed to make Emacs work on this
  36    system.  For example, you might define certain system call names
  37    that don't exist on your system, or that do different things on
  38    your system and must be used only through an encapsulation (which
  39    you should place, by convention, in sysdep.c).  */
  40
  41 /* ============================================================ */
  42
  43 /* After adding support for a new system, modify the large case
  44    statement in configure.ac to recognize reasonable
  45    configuration names, and add a description of the system to
  46    `etc/MACHINES'.
  47
  48    Check for any tests of $opsys in configure.ac, and add an entry
  49    for the new system if needed.
  50
  51    If you've just fixed a problem in an existing configuration file,
  52    you should also check `etc/MACHINES' to make sure its descriptions
  53    of known problems in that configuration should be updated.  */