aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEli Zaretskii2013-05-01 20:35:46 +0300
committerEli Zaretskii2013-05-01 20:35:46 +0300
commit10f81f3ac90f98160f611787e20dcad96bb500e9 (patch)
tree3394d8f69fadbc7411f3f3404402263175ce594f
parent9c1a1306117d5c41be1beac981d33085fa0fe5a1 (diff)
downloademacs-10f81f3ac90f98160f611787e20dcad96bb500e9.tar.gz
emacs-10f81f3ac90f98160f611787e20dcad96bb500e9.zip
Improve INSTALL.MSYS instructions given feedback from Dani Moncayo.
-rw-r--r--nt/INSTALL.MSYS88
1 files changed, 67 insertions, 21 deletions
diff --git a/nt/INSTALL.MSYS b/nt/INSTALL.MSYS
index c1b287083f6..35895e0a227 100644
--- a/nt/INSTALL.MSYS
+++ b/nt/INSTALL.MSYS
@@ -84,17 +84,12 @@ Windows 9X as well).
84 A correct installation makes all the rest almost trivial; a botched 84 A correct installation makes all the rest almost trivial; a botched
85 installation will likely make you miserable for quite some time. 85 installation will likely make you miserable for quite some time.
86 86
87** Installing MinGW 87 There are two alternative to installing MinGW + MSYS: using the GUI
88 installer, called mingw-get, provided by the MinGW project, or
89 manual installation. The next two sections describe each one of
90 these.
88 91
89 You will need to install the MinGW port of GCC and Binutils, and the 92** Installing MinGW and MSYS using mingw-get
90 MinGW runtime and Windows API distributions, to compile Emacs. You
91 can find these on the MinGW download/Base page:
92
93 https://sourceforge.net/projects/mingw/files/MinGW/Base/
94
95 In general, install the latest stable versions of the following
96 MinGW packages from that page: gcc, binutils, mingw-rt, w32api. You
97 only need the 'bin' and the 'dll' tarballs of each of the above.
98 93
99 A nice GUI installer, called mingw-get, is available for those who 94 A nice GUI installer, called mingw-get, is available for those who
100 don't like to mess with manual installations. You can download it 95 don't like to mess with manual installations. You can download it
@@ -105,11 +100,42 @@ Windows 9X as well).
105 (This installer only supports packages downloaded from the MinGW 100 (This installer only supports packages downloaded from the MinGW
106 site; for the rest you will still need the manual method.) 101 site; for the rest you will still need the manual method.)
107 102
108 MinGW and MSYS packages are distributed as .tar.lzma compressed 103 After installing mingw-get, invoke it install the packages that are
109 archives. If you like to install the packages manually, then we 104 already selected by default on the "Select Components" screen of its
110 recommend to use the Windows port of the 'bsdtar' program to unpack 105 wizard.
111 the tarballs. 'bsdtar' is available as part of the 'libarchive' 106
112 package from here: 107 After that, use "ming-get install PACKAGE" to install the following
108 additional packages:
109
110 . msys-base
111 . mingw-developer-toolkit
112 . msys-automake
113
114 At this point, you should be ready to configure and build Emacs in
115 its basic configuration. Skip to the "Generating the configure
116 script" section for the build instructions. If you want to build it
117 with image support and other optional libraries, read about the
118 optional libraries near the end of this document, before you start
119 the build.
120
121** Installing MinGW and MSYS manually
122
123*** MinGW
124
125 You will need to install the MinGW port of GCC and Binutils, and the
126 MinGW runtime and Windows API distributions, to compile Emacs. You
127 can find these on the MinGW download/Base page:
128
129 https://sourceforge.net/projects/mingw/files/MinGW/Base/
130
131 In general, install the latest stable versions of the following
132 MinGW packages from that page: gcc, binutils, mingw-rt, w32api. You
133 only need the 'bin' and the 'dll' tarballs of each of the above.
134
135 MinGW packages are distributed as .tar.lzma compressed archives. To
136 install the packages manually, we recommend to use the Windows port
137 of the 'bsdtar' program to unpack the tarballs. 'bsdtar' is
138 available as part of the 'libarchive' package from here:
113 139
114 http://sourceforge.net/projects/ezwinports/files/ 140 http://sourceforge.net/projects/ezwinports/files/
115 141
@@ -118,7 +144,7 @@ Windows 9X as well).
118 C:. A typical example would be D:\usr, with D:\usr\bin holding the 144 C:. A typical example would be D:\usr, with D:\usr\bin holding the
119 binaries and DLLs (should be added to your Path environment 145 binaries and DLLs (should be added to your Path environment
120 variable), D:\usr\include holding the include files, D:\usr\lib 146 variable), D:\usr\include holding the include files, D:\usr\lib
121 holding the static and import libraries, D:\share holding docs, 147 holding the static and import libraries, D:\usr\share holding docs,
122 message catalogs, and package-specific subdirectories, etc. 148 message catalogs, and package-specific subdirectories, etc.
123 149
124 Having all the headers and libraries in a single place will greatly 150 Having all the headers and libraries in a single place will greatly
@@ -144,7 +170,8 @@ Windows 9X as well).
144 170
145 Available from http://gnuwin32.sourceforge.net/packages/gzip.htm. 171 Available from http://gnuwin32.sourceforge.net/packages/gzip.htm.
146 172
147 . pkg-config (needed for building with some optional image libraries) 173 . pkg-config (needed for building with some optional libraries,
174 such as GnuTLS and libxml2)
148 175
149 Available from http://www.gtk.org/download/win32.php 176 Available from http://www.gtk.org/download/win32.php
150 177
@@ -160,7 +187,7 @@ Windows 9X as well).
160 building a trivial "hello, world!" program, and make sure that it 187 building a trivial "hello, world!" program, and make sure that it
161 builds without any error messages and the binary works when run. 188 builds without any error messages and the binary works when run.
162 189
163** Installing MSYS 190*** Installing MSYS
164 191
165 You will also need a reasonably full MSYS installation. MSYS is an 192 You will also need a reasonably full MSYS installation. MSYS is an
166 environment needed to run the Posix configure scripts and the 193 environment needed to run the Posix configure scripts and the
@@ -193,6 +220,10 @@ Windows 9X as well).
193 http://sourceforge.net/projects/ezwinports/files/automake-1.11.6-msys-bin.zip/download 220 http://sourceforge.net/projects/ezwinports/files/automake-1.11.6-msys-bin.zip/download
194 http://sourceforge.net/projects/ezwinports/files/autoconf-2.65-msys-bin.zip/download 221 http://sourceforge.net/projects/ezwinports/files/autoconf-2.65-msys-bin.zip/download
195 222
223 MSYS packages are distributed as .tar.lzma compressed archives. To
224 install the packages manually, we recommend to use the Windows port
225 of the 'bsdtar' program, already mentioned above.
226
196 If/when you are confident in your MinGW/MSYS installation, and want 227 If/when you are confident in your MinGW/MSYS installation, and want
197 to speed up the builds, we recommend installing a pre-release 228 to speed up the builds, we recommend installing a pre-release
198 version of Make from here: 229 version of Make from here:
@@ -229,10 +260,10 @@ Windows 9X as well).
229 need. 260 need.
230 261
231 At this point, you are ready to build Emacs in its basic 262 At this point, you are ready to build Emacs in its basic
232 configuration. If you want to build it with image support, read 263 configuration. If you want to build it with image support and other
233 about the optional image libraries near the end of this document. 264 optional libraries, read about that near the end of this document.
234 265
235* Generating the configure script. 266* Generating the configure script
236 267
237 If you are building a release or pretest tarball, skip this section, 268 If you are building a release or pretest tarball, skip this section,
238 because the configure script is already present in the tarball. 269 because the configure script is already present in the tarball.
@@ -493,6 +524,11 @@ Windows 9X as well).
493 524
494* Optional GnuTLS support 525* Optional GnuTLS support
495 526
527 To compile with GnuTLS, you will need pkg-config to be installed, as
528 the configure script invokes pkg-config to find out which compiler
529 switches to use for GnuTLS. See above for the URL where you can
530 find pkg-config for Windows.
531
496 If the configure script finds the gnutls/gnutls.h file in the 532 If the configure script finds the gnutls/gnutls.h file in the
497 include path, Emacs is built with GnuTLS support by default; to 533 include path, Emacs is built with GnuTLS support by default; to
498 avoid that you can pass the argument --without-gnutls. 534 avoid that you can pass the argument --without-gnutls.
@@ -507,6 +543,11 @@ Windows 9X as well).
507 543
508* Optional libxml2 support 544* Optional libxml2 support
509 545
546 To compile with libxml2, you will need pkg-config to be installed,
547 as the configure script invokes pkg-config to find out which
548 compiler switches to use for libxml2. See above for the URL where
549 you can find pkg-config for Windows.
550
510 If the configure script finds the libxml/HTMLparser.h file in the 551 If the configure script finds the libxml/HTMLparser.h file in the
511 include path, Emacs is built with libxml2 support by default; to 552 include path, Emacs is built with libxml2 support by default; to
512 avoid that you can pass the argument --without-libxml2. 553 avoid that you can pass the argument --without-libxml2.
@@ -533,6 +574,11 @@ Windows 9X as well).
533 574
534* Experimental SVG support 575* Experimental SVG support
535 576
577 To compile with SVG, you will need pkg-config to be installed, as
578 the configure script invokes pkg-config to find out which compiler
579 switches to use for SVG. See above for the URL where you can find
580 pkg-config for Windows.
581
536 SVG support is currently experimental, and not built by default. 582 SVG support is currently experimental, and not built by default.
537 Specify --with-rsvg and ensure you have all the dependencies in your 583 Specify --with-rsvg and ensure you have all the dependencies in your
538 include path. Unless you have built a minimalist librsvg yourself 584 include path. Unless you have built a minimalist librsvg yourself