* coding.h (decode_coding_string, encode_coding_string): Use
[bpt/emacs.git] / msdos / INSTALL
CommitLineData
cafb9504
EZ
1GNU Emacs Installation Guide for the DJGPP (a.k.a. MS-DOS) port
2
3Copyright (C) 1992, 1994, 1996, 1997, 2000, 2001, 2002, 2003, 2004,
f5d0ac07 42005, 2006, 2007, 2008, 2009 Free Software Foundation, Inc.
cafb9504
EZ
5See the end of the file for license conditions.
6
7The DJGPP port of GNU Emacs builds and runs on plain DOS and also on
8all versions of MS-Windows from version 3.X on, including Windows XP
9and Vista.
10
11To build and install the DJGPP port, you need to have the DJGPP ports
12of GCC (the GNU C compiler), GNU Make, rm, mv, and sed. See the
13remarks in CONFIG.BAT for more information about locations and
14versions. The Emacs FAQ (see info/efaq) includes pointers to Internet
15sites where you can find the necessary utilities; search for "MS-DOS".
16The configuration step (see below) will test for these utilities and
17will refuse to continue if any of them isn't found.
18
71a69201
EZ
19Bootstrapping Emacs or recompiling Lisp files in the `lisp'
20subdirectory using the various targets in the lisp/Makefile file
21requires additional utilities: `find' (from Findutils), GNU `echo' and
22`test' (from Sh-utils), `ls' and `chmod' (from Fileutils), `grep'
23(from Grep), and a port of Bash. However, you should not normally
24need to run lisp/Makefile, as all the Lisp files are distributed in
25byte-compiled form as well. As for bootstrapping, you will only need
26that if you check-out development sources from the Emacs source
ead9233b
EZ
27repository. (Note: If you are checking out of CVS, use the -kb option
28of the `checkout' and `update' commands, to preserve the original
29Unix-style EOL format of the files. If some Lisp files are converted
30to DOS format, the build might fail.)
cafb9504 31
ac97579c 32If you are building the DJGPP version of Emacs on a DOS-like system
cafb9504
EZ
33which supports long file names (e.g. Windows 9X or Windows XP), you
34need to make sure that long file names are handled consistently both
35when you unpack the distribution and compile it. If you intend to
36compile with DJGPP v2.0 or later, and long file names support is
37enabled (LFN=y in the environment), you need to unpack Emacs
38distribution in a way that doesn't truncate the original long
39filenames to the DOS 8.3 namespace; the easiest way to do this is to
40use djtar program which comes with DJGPP, since it will note the LFN
41setting and behave accordingly. You can build Emacs with LFN=n, if
42some of your tools don't support long file names: just ensure that LFN
43is set to `n' during both unpacking and compiling.
44
45(By the time you read this, you have already unpacked the Emacs
46distribution, but if the explanations above imply that you should have
47done it differently, it's safer to delete the directory tree created
48by the unpacking program and unpack Emacs again, than to risk running
49into problems during the build process.)
50
51It is important to understand that the runtime support of long file
52names by the Emacs binary is NOT affected by the LFN setting during
53compilation; Emacs compiled with DJGPP v2.0 or later will always
54support long file names on Windows no matter what was the setting
55of LFN at compile time. However, if you compiled with LFN disabled
56and want to enable LFN support after Emacs was already built, you need
57to make sure that the support files in the lisp, etc and info
58directories are called by their original long names as found in the
59distribution. You can do this either by renaming the files manually,
60or by extracting them from the original distribution archive with
61djtar after you set LFN=y in the environment.
62
63To unpack Emacs with djtar, type this command:
64
65 djtar -x emacs.tgz
66
67(This assumes that the Emacs distribution is called `emacs.tgz' on
68your system.)
69
70If you want to print international characters, install the intlfonts
71distribution. For this, create a directory called `fonts' under the
72Emacs top-level directory (usually called `emacs-XX.YY') created by
73unpacking emacs.tgz, chdir into the directory emacs-XX.YY/fonts, and
74type this:
75
76 djtar -x intlfonts.tgz
77
78When unpacking Emacs is done, a directory called `emacs-XX.YY' will be
79created, where XX.YY is the Emacs version. To build and install
80Emacs, chdir to that directory and type these commands:
81
82 config msdos
83 make install
84
85Running "config msdos" checks for several programs that are required
86to configure and build Emacs; if one of those programs is not found,
87CONFIG.BAT stops and prints an error message. If you have DJGPP
88version 2.0 or 2.01, it will complain about a program called
89DJECHO.EXE. These old versions of DJGPP shipped that program under
90the name ECHO.EXE, so you can simply copy ECHO.EXE to DJECHO.EXE and
91rerun CONFIG.BAT. If you have neither ECHO.EXE nor DJECHO.EXE, you
92should be able to find them in your djdevNNN.zip archive (where NNN is
93the DJGPP version number).
94
95On Windows NT, Windows 2000/XP/Vista, running "config msdos" might
96print an error message like "VDM has been already loaded". This is
97because those systems have a program called `redir.exe' which is
98incompatible with a program by the same name supplied with DJGPP,
99which is used by config.bat. To resolve this, move the DJGPP's `bin'
100subdirectory to the front of your PATH environment variable.
101
bd448b7a
EZ
102Windows Vista has several bugs in its DPMI server related to memory
103allocation: it fails DPMI resize memory block function, and it
104arbitrarily limits the default amount of DPMI memory to 32MB. To work
105around these bugs, first configure Emacs to use the `malloc' function
106from the DJGPP library. To this end, run CONFIG.BAT with the
107"--with-system-malloc" option:
108
109 config --with-system-malloc msdos
110 make install
111
112In addition, you'll need to install Service Pack 1 (SP1) or later to
113Windows Vista and enlarge its DPMI memory limit by setting the value
114of this Registry key:
115
116 HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Wow\DpmiLimit
117
118Create this key if it does not exist. The value is a DWORD; setting
119it to 536870912 should let Emacs use up to 512MB of memory.
120
d7d1c408
EZ
121If you have other problems, either building Emacs or running the
122produced binary, look in the file etc/PROBLEMS for some known problems
123related to the DJGPP port (search for "MS-DOS").
124
cafb9504
EZ
125To install the international fonts, chdir to the intlfonts-X.Y
126directory created when you unpacked the intlfonts distribution (X.Y is
127the version number of the fonts' distribution), and type the following
128command:
129
130 make bdf INSTALLDIR=..
131
132After Make finishes, you may remove the directory intlfonts-X.Y; the
133fonts are installed into the fonts/bdf subdirectory of the top-level
134Emacs directory, and that is where Emacs will look for them by
135default.
136
137Building Emacs creates executable files in the src and lib-src
138directories. Installing the DJGPP port of Emacs moves these
139executables to a sibling directory called bin. For example, if you
140build in directory C:/emacs, installing moves the executables from
141C:/emacs/src and C:/emacs/lib-src to the directory C:/emacs/bin, so
142you can then delete the subdirectories C:/emacs/src and
143C:/emacs/lib-src if you wish. The only subdirectories you need to
144keep are bin, lisp, etc and info. (If you installed intlfonts, keep
145the fonts directory and all its subdirectories as well.) The bin
146subdirectory should be added to your PATH. The msdos subdirectory
147includes a PIF and an icon file for Emacs which you might find useful
148if you run Emacs under MS Windows.
149
150Emacs on MSDOS finds the lisp, etc and info directories by looking in
151../lisp, ../etc and ../info, starting from the directory where the
152Emacs executable was run from. You can override this by setting the
153environment variables EMACSDATA (for the location of `etc' directory),
154EMACSLOADPATH (for the location of `lisp' directory) and INFOPATH (for
155the location of the `info' directory).
156
157Emacs features which require asynchronous subprocesses that depend on
158multitasking do not work in the DJGPP port. Synchronous subprocesses
159do work, so features such as compilation and grep run synchronously,
160unlike opn other platforms.
161
162Version 2.0 of djgpp has two bugs that affect Emacs. We've included
163corrected versions of two files from djgpp in the msdos subdirectory:
164is_exec.c and sigaction.c. To work around the bugs, compile these
165files and link them into temacs. Djgpp versions 2.01 and later have
166these bugs fixed, so upgrade if you can before building Emacs.
167
168\f
169This file is part of GNU Emacs.
170
171GNU Emacs is free software: you can redistribute it and/or modify
172it under the terms of the GNU General Public License as published by
173the Free Software Foundation, either version 3 of the License, or
174(at your option) any later version.
175
176GNU Emacs is distributed in the hope that it will be useful,
177but WITHOUT ANY WARRANTY; without even the implied warranty of
178MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
179GNU General Public License for more details.
180
181You should have received a copy of the GNU General Public License
182along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>.