7 |
If you used WinZip to unpack the distribution, we suggest to |
If you used WinZip to unpack the distribution, we suggest to |
8 |
remove the files and unpack again with a different program! |
remove the files and unpack again with a different program! |
9 |
WinZip is known to create some subtle and hard to debug problems, |
WinZip is known to create some subtle and hard to debug problems, |
10 |
such as converting files to DOS CR-LF format, not creating empty |
such as converting files to DOS CR-LF format, not creating empty |
11 |
directories, etc. We suggest to use djtarnt.exe from the GNU FTP |
directories, etc. We suggest to use djtarnt.exe from the GNU FTP |
12 |
site. |
site. |
13 |
|
|
18 |
build (latest versions of the Cygwin toolkit, at least since v1.3.3, |
build (latest versions of the Cygwin toolkit, at least since v1.3.3, |
19 |
include the MinGW headers and libraries as an integral part). |
include the MinGW headers and libraries as an integral part). |
20 |
|
|
21 |
|
Other compilers may work, but specific reports from people that have |
22 |
|
tried suggest that the Intel C compiler (for example) may produce an |
23 |
|
Emacs executable with strange filename completion behaviour. Unless |
24 |
|
you would like to assist by finding and fixing the cause of any bugs |
25 |
|
like this, we recommend the use of the supported compilers mentioned |
26 |
|
in the previous paragraph. |
27 |
|
|
28 |
If you build Emacs on Windows 9X or ME, not on Windows 2000 or |
If you build Emacs on Windows 9X or ME, not on Windows 2000 or |
29 |
Windows NT, we suggest to install the Cygwin port of Bash. |
Windows NT, we suggest to install the Cygwin port of Bash. |
30 |
|
|
42 |
In addition, using 4NT as your shell is known to fail the build process, |
In addition, using 4NT as your shell is known to fail the build process, |
43 |
at least for 4NT version 3.01. Use cmd.exe, the default NT shell, |
at least for 4NT version 3.01. Use cmd.exe, the default NT shell, |
44 |
instead. |
instead. |
45 |
|
|
46 |
sh exists no sh |
sh exists no sh |
47 |
|
|
48 |
cygwin b20.1 make (3.75): fails[1, 5] fails[2, 5] |
cygwin b20.1 make (3.75): fails[1, 5] fails[2, 5] |
53 |
cygwin compiled gmake 3.77: fails[1, 5] fails[2, 5] |
cygwin compiled gmake 3.77: fails[1, 5] fails[2, 5] |
54 |
cygwin compiled make 3.78.1: fails[5] fails[2, 5] |
cygwin compiled make 3.78.1: fails[5] fails[2, 5] |
55 |
cygwin compiled make 3.79.1: fails[3, 5] fails[2?, 5] |
cygwin compiled make 3.79.1: fails[3, 5] fails[2?, 5] |
56 |
mingw32 compiled make 3.79.1: okay okay |
mingw32 compiled make 3.79.1: okay okay |
57 |
|
|
58 |
Notes: |
Notes: |
59 |
|
|
82 |
is running, when gcc support is being tested. These cannot be |
is running, when gcc support is being tested. These cannot be |
83 |
surpressed because of limitations in the Windows 9x command.com shell. |
surpressed because of limitations in the Windows 9x command.com shell. |
84 |
|
|
85 |
|
* Optional image library support |
86 |
|
|
87 |
|
To build Emacs with support for PNG images, the libpng and zlib |
88 |
|
headers must be in the include path when the configure script is |
89 |
|
run. This can be setup using environment variables, or by |
90 |
|
specifying --cflags -I... options on the command-line to |
91 |
|
configure.bat. Similarly, the jpeg-6b, libXpm, tiff and libungif |
92 |
|
headers need to be in the include path for support for those image |
93 |
|
formats to work. The configure script will report whether it was |
94 |
|
able to detect the headers. |
95 |
|
|
96 |
|
To use the PNG support, zlib.dll (or zlibd.dll) and libpng.dll (or |
97 |
|
libpng13.dll, or libpng13d.dll) must be on the PATH or in the same |
98 |
|
directory as emacs.exe when Emacs is started. Similar instructions |
99 |
|
apply for other image libraries. Note that tiff support depends on |
100 |
|
the jpeg library. If you did not compile the libraries yourself, you |
101 |
|
must make sure that the jpeg library you install is the same one |
102 |
|
that the tiff library was compiled against. |
103 |
|
|
104 |
* Building |
* Building |
105 |
|
|
106 |
After running configure, simply run the appropriate `make' program for |
After running configure, simply run the appropriate `make' program for |