nt/INSTALL.MSYS

   1                     Building and Installing Emacs on MS-Windows
   2                           using the MSYS and MinGW tools
   3
   4   Copyright (C) 2013 Free Software Foundation, Inc.
   5   See the end of the file for license conditions.
   6
   7 The MSYS/MinGW build described here is supported on versions of
   8 Windows starting with Windows 2000 and newer.  Windows 9X are not
   9 supported (but the Emacs binary produced by this build will run on
  10 Windows 9X as well).
  11
  12 * For the brave (a.k.a. "impatient"):
  13
  14   For those who have a working MSYS/MinGW development environment and
  15   are comfortable with running Posix configure scripts, here are the
  16   concise instructions for configuring and building the native Windows
  17   binary of Emacs with these tools.
  18
  19   Do not use this recipe with Cygwin.  For building on Cygwin, use the
  20   normal installation instructions, ../INSTALL.
  21
  22   Do not use these instructions if you don't have MSYS installed; for
  23   that, see the file INSTALL in this directory.
  24
  25   0. Start the MSYS Bash window.  Everything else below is done from
  26      that window's Bash prompt.
  27
  28   0a. If you are building from the development trunk (as opposed to a
  29       release tarball), produce the configure script, by typing from
  30       the top-level Emacs source directory:
  31
  32       ./autogen.sh
  33
  34   1. If you want to build Emacs outside of the source tree
  35      (recommended), create the build directory and chdir there.
  36
  37   2. Invoke the MSYS-specific configure script:
  38
  39       - If you are building outside the source tree:
  40
  41         /PATH/TO/EMACS/SOURCE/TREE/nt/msysconfig.sh --prefix=PREFIX ...
  42
  43       - If you are building in-place, i.e. inside the source tree:
  44
  45         ./nt/msysconfig.sh --prefix=PREFIX ...
  46
  47      It is always preferable to use --prefix to configure Emacs for
  48      some specific location of its installed tree; the default
  49      /usr/local is not suitable for Windows (see the detailed
  50      instructions for the reasons).
  51
  52      You can pass other options to the configure script.  Here's a
  53      typical example (for an in-place debug build):
  54
  55        CPPFLAGS='-DGLYPH_DEBUG=1' CFLAGS='-O0 -g3' ./nt/msysconfig.sh --prefix=d:/usr/emacs --enable-checking
  56
  57   3. After the configure script finishes, it should display the
  58      resulting configuration.  After that, type
  59
  60        make
  61
  62      Use "make -j N" if your MSYS Make supports parallel execution;
  63      the build will take significantly less time in that case.  Here N
  64      is the number of simultaneous parallel jobs; use the number of
  65      the cores on your system.
  66
  67   4. Install the produced binaries:
  68
  69        make install
  70
  71      If you want the installation tree to go to a place that is
  72      different from the one specified by --prefix, say
  73
  74        make install prefix=/where/ever/you/want
  75
  76   That's it!
  77
  78   If these short instructions somehow fail, read the rest of this
  79   file.
  80
  81 * Installing MinGW and MSYS
  82
  83   Make sure you carefully read the following two sections in their
  84   entirety and install/configure the various packages as instructed.
  85   A correct installation makes all the rest almost trivial; a botched
  86   installation will likely make you miserable for quite some time.
  87
  88   There are two alternative to installing MinGW + MSYS: using the GUI
  89   installer, called mingw-get, provided by the MinGW project, or
  90   manual installation.  The next two sections describe each one of
  91   these.
  92
  93 ** Installing MinGW and MSYS using mingw-get
  94
  95   A nice GUI installer, called mingw-get, is available for those who
  96   don't like to mess with manual installations.  You can download it
  97   from here:
  98
  99     https://sourceforge.net/projects/mingw/files/Installer/mingw-get/
 100
 101   (This installer only supports packages downloaded from the MinGW
 102   site; for the rest you will still need the manual method.)
 103
 104   After installing mingw-get, invoke it to install the packages that
 105   are already selected by default on the "Select Components" screen of
 106   its wizard.
 107
 108   After that, use "mingw-get install PACKAGE" to install the following
 109   additional packages:
 110
 111    . msys-base
 112    . mingw-developer-toolkit
 113    . msys-automake
 114
 115   (We recommend that you refrain from installing the MSYS Texinfo
 116   package, which is part of msys-base, because it might produce mixed
 117   EOL format when installing Info files.  Instead, install the MinGW
 118   port of Texinfo, see the ezwinports URL below.  To uninstall the
 119   MSYS Texinfo, after installing it as part of msys-base, invoke the
 120   command "mingw-get remove msys-texinfo".)
 121
 122   At this point, you should be ready to configure and build Emacs in
 123   its basic configuration.  Skip to the "Generating the configure
 124   script" section for the build instructions.  If you want to build it
 125   with image support and other optional libraries, read about the
 126   optional libraries near the end of this document, before you start
 127   the build.  Also, consider installing additional MinGW packages that
 128   are required/recommended, especially if you are building from the
 129   Bazaar repository, as described in the next section.
 130
 131 ** Installing MinGW and MSYS manually
 132
 133 *** MinGW
 134
 135   You will need to install the MinGW port of GCC and Binutils, and the
 136   MinGW runtime and Windows API distributions, to compile Emacs.  You
 137   can find these on the MinGW download/Base page:
 138
 139     https://sourceforge.net/projects/mingw/files/MinGW/Base/
 140
 141   In general, install the latest stable versions of the following
 142   MinGW packages from that page: gcc, binutils, mingw-rt, w32api.  You
 143   only need the 'bin' and the 'dll' tarballs of each of the above.
 144
 145   MinGW packages are distributed as .tar.lzma compressed archives.  To
 146   install the packages manually, we recommend to use the Windows port
 147   of the 'bsdtar' program to unpack the tarballs.  'bsdtar' is
 148   available as part of the 'libarchive' package from here:
 149
 150     http://sourceforge.net/projects/ezwinports/files/
 151
 152   The recommended place to install these packages is a single tree
 153   starting from some directory on a drive other than the system drive
 154   C:.  A typical example would be D:\usr, with D:\usr\bin holding the
 155   binaries and DLLs (should be added to your Path environment
 156   variable), D:\usr\include holding the include files, D:\usr\lib
 157   holding the static and import libraries, D:\usr\share holding docs,
 158   message catalogs, and package-specific subdirectories, etc.
 159
 160   Having all the headers and libraries in a single place will greatly
 161   reduce the number of -I and -L flags you will have to pass to the
 162   configure script (see below), as these files will be right where the
 163   compiler expects them.
 164
 165   We specifically do NOT recommend installing packages below
 166   "C:\Program Files" or "C:\Program Files (x86)".  These directories
 167   are protected on versions of Windows from Vista and on, and you will
 168   have difficulties updating and maintaining your installation later,
 169   due to UAC elevation prompts, file virtualization, etc.  You *have*
 170   been warned!
 171
 172   Additional MinGW packages are required/recommended, especially if
 173   you are building from the Bazaar repository:
 174
 175    . Texinfo (needed to produce the Info manuals when building from
 176      bzr, and for "make install")
 177
 178      Available from http://sourceforge.net/projects/ezwinports/files/.
 179
 180    . gzip (needed to compress files during "make install")
 181
 182      Available from http://gnuwin32.sourceforge.net/packages/gzip.htm.
 183
 184    . pkg-config (needed for building with some optional libraries,
 185      such as GnuTLS and libxml2)
 186
 187      Available from http://www.gtk.org/download/win32.php
 188
 189   Each package might list other packages as prerequisites on its
 190   download page (under "Runtime requirements"); download those as
 191   well.  (Using the GUI installer mingw-get will fetch those
 192   prerequisites automatically for you.)  A missing prerequisite will
 193   manifest itself by the program failing to run and presenting a
 194   pop-up dialog that states the missing or incompatible DLL; be sure
 195   to find and install these missing DLLs.
 196
 197   Once you think you have MinGW installed, test the installation by
 198   building a trivial "hello, world!" program, and make sure that it
 199   builds without any error messages and the binary works when run.
 200
 201 *** MSYS
 202
 203   You will need a reasonably full MSYS installation.  MSYS is an
 204   environment needed to run the Posix configure scripts and the
 205   resulting Makefile's, in order to produce native Windows binaries
 206   using the MinGW compiler and runtime libraries.  Here's the list of
 207   MSYS packages that are required:
 208
 209    . All the packages from the MSYS Base distribution, listed here:
 210
 211      https://sourceforge.net/projects/mingw/files/MSYS/Base/
 212
 213    . Additional packages listed below, from the MSYS Extension
 214      distribution here:
 215
 216      https://sourceforge.net/projects/mingw/files/MSYS/Extension/
 217
 218       - flex
 219       - bison
 220       - m4
 221       - perl
 222       - mktemp
 223
 224      These should only be needed if you intend to build development
 225      versions of Emacs from the Bazaar repository.
 226
 227    . Additional packages (needed only if building from the Bazaar
 228      repository): Automake and Autoconf.  They are available from
 229      here:
 230
 231      http://sourceforge.net/projects/ezwinports/files/automake-1.11.6-msys-bin.zip/download
 232      http://sourceforge.net/projects/ezwinports/files/autoconf-2.65-msys-bin.zip/download
 233
 234   MSYS packages are distributed as .tar.lzma compressed archives.  To
 235   install the packages manually, we recommend to use the Windows port
 236   of the 'bsdtar' program, already mentioned above.
 237
 238   If/when you are confident in your MinGW/MSYS installation, and want
 239   to speed up the builds, we recommend installing a pre-release
 240   version of Make from here:
 241
 242      https://sourceforge.net/projects/mingwbuilds/files/external-binary-packages/
 243
 244   These are snapshot builds of many packages, but you only need
 245   make.exe from there.  The advantage of this make.exe is that it
 246   supports parallel builds, so you can use "make -j N" to considerably
 247   speed up your builds
 248
 249   For each of these packages, install the 'bin' and 'dll' tarballs of
 250   their latest stable releases.  If there's an 'ext' tarball (e.g.,
 251   msysCORE and Coreutils have it), download and install those as well.
 252
 253   Each package might list other packages as prerequisites on its
 254   download page (under "Runtime requirements"); download those as
 255   well.  (Using the GUI installer mingw-get will fetch those
 256   prerequisites automatically for you.)  A missing prerequisite will
 257   manifest itself by the program failing to run and presenting a
 258   pop-up dialog that states the missing or incompatible DLL; be sure
 259   to find and install these missing DLLs.
 260
 261   MSYS packages should be installed in a separate tree from MinGW.
 262   For example, use D:\MSYS or D:\usr\MSYS as the top-level directory
 263   from which you unpack all of the MSYS packages.
 264
 265   Do NOT add the MSYS bin directory to your Windows Path!  Only the
 266   MinGW bin directory should be on Path.  When you install MSYS, it
 267   creates a shortcut on your desktop that invokes the MSYS Bash shell
 268   in a Command Prompt window; that shell is already set up so that the
 269   MSYS bin directory is on PATH ahead of any other directory.  Thus,
 270   Bash will find MSYS executables first, which is exactly what you
 271   need.
 272
 273   At this point, you are ready to build Emacs in its basic
 274   configuration.  If you want to build it with image support and other
 275   optional libraries, read about that near the end of this document.
 276
 277 * Generating the configure script
 278
 279   If you are building a release or pretest tarball, skip this section,
 280   because the configure script is already present in the tarball.
 281
 282   To build a development snapshot from the Emacs Bazaar repository,
 283   you will first need to generate the configure script and a few other
 284   auto-generated files.  (If this step, described below, somehow
 285   fails, you can use the files in the autogen/ directory instead, but
 286   they might be outdated, and, most importantly, you are well advised
 287   not to disregard any failures in your local build procedures, as
 288   these are likely to be symptoms of incorrect installation that will
 289   bite you down the road.)
 290
 291   To generate the configure script, type this at the MSYS Bash prompt
 292   from the top-level directory of the Emacs tree:
 293
 294      ./autogen.sh
 295
 296   If successful, this command should produce the following output:
 297
 298      $ ./autogen.sh
 299      Checking whether you have the necessary tools...
 300      (Read INSTALL.BZR for more details on building Emacs)
 301
 302      Checking for autoconf (need at least version 2.65)...
 303      ok
 304      Checking for automake (need at least version 1.11)...
 305      ok
 306      Your system has the required tools, running autoreconf...
 307      You can now run `./configure'.
 308
 309 * Configuring Emacs for MinGW:
 310
 311   Now it's time to run the configure script.  You can do that either
 312   from a separate build directory that is outside of the Emacs source
 313   tree (recommended), or from inside the source tree.  The former is
 314   recommended because it allows you to have several different builds,
 315   e.g., an optimized build and an unoptimized one, of the same
 316   revision of the source tree; the source tree will be left in its
 317   pristine state, without any build products.
 318
 319   You invoke the configure script like this:
 320
 321      /PATH/TO/EMACS/SOURCE/TREE/nt/msysconfig.sh --prefix=PREFIX ...
 322
 323   or, if you are building in-place, i.e. inside the source tree:
 324
 325      ./nt/msysconfig.sh --prefix=PREFIX ...
 326
 327   Here PREFIX is the place where you eventually want to install Emacs
 328   once built, e.g. d:/usr.  We recommend to always use --prefix when
 329   building Emacs on Windows, because the default '/usr/local' is not
 330   appropriate for Windows: it will be mapped by MSYS to something like
 331   C:\MSYS\local, and it will defeat the purpose of PREFIX, which is to
 332   install programs in a single coherent tree resembling Posix systems.
 333   Such a single-tree installation makes sure all the other programs
 334   and packages ported from GNU or Unix systems will work seamlessly
 335   together.  Where exactly is the root of that tree on your system is
 336   something only you, the user who builds Emacs, can know, and the
 337   Emacs build process cannot guess, because usually there's no
 338   '/usr/local' directory on any drive on Windows systems.
 339
 340   You can pass additional options to the configure script, for the
 341   full list type
 342
 343      ./nt/msysconfig.sh --help
 344
 345   As explained in the help text, you may need to tell the script what
 346   are the optional flags to invoke the compiler.  This is needed if
 347   some of your headers and libraries, e.g., those belonging to
 348   optional image libraries, are installed in places where the compiler
 349   normally doesn't look for them.  (Remember that advice above to
 350   avoid such situations? here's is where you will start paying for
 351   disregarding that recommendation.)  For example, if you have libpng
 352   headers in C:\emacs\libs\libpng-1.2.37-lib\include and jpeg library
 353   headers in C:\emacs\libs\jpeg-6b-4-lib\include, you will need to say
 354   something like this:
 355
 356     CPPFLAGS='-Ic:/emacs/libs/libpng-1.2.37-lib/include -Ic:/emacs/libs/jpeg-6b-4-lib/include' ./nt/msysconfig.sh --prefix=PREFIX
 357
 358   which is quite a mouth-full, especially if you have more directories
 359   to specify...  Perhaps you may wish to revisit your installation
 360   decisions now.
 361
 362   A few frequently used options are needed when you want to produce an
 363   unoptimized binary with runtime checks enabled:
 364
 365      CPPFLAGS='-DGLYPH_DEBUG=1' CFLAGS='-O0 -g3' ./nt/msysconfig.sh --prefix=PREFIX --enable-checking
 366
 367   Once invoked, the configure script will run for some time, and, if
 368   successful, will eventually produce a summary of the configuration
 369   like this:
 370
 371      Configured for `i686-pc-mingw32'.
 372
 373        Where should the build process find the source code?    /path/to/emacs/sources
 374        What compiler should emacs be built with?               gcc  -std=gnu99 -O0 -g3
 375        Should Emacs use the GNU version of malloc?             yes
 376        Should Emacs use a relocating allocator for buffers?    yes
 377        Should Emacs use mmap(2) for buffer allocation?         no
 378        What window system should Emacs use?                    w32
 379        What toolkit should Emacs use?                          none
 380        Where do we find X Windows header files?                NONE
 381        Where do we find X Windows libraries?                   NONE
 382        Does Emacs use -lXaw3d?                                 no
 383        Does Emacs use -lXpm?                                   yes
 384        Does Emacs use -ljpeg?                                  yes
 385        Does Emacs use -ltiff?                                  yes
 386        Does Emacs use a gif library?                           yes
 387        Does Emacs use -lpng?                                   yes
 388        Does Emacs use -lrsvg-2?                                no
 389        Does Emacs use imagemagick?                             no
 390        Does Emacs use -lgpm?                                   no
 391        Does Emacs use -ldbus?                                  no
 392        Does Emacs use -lgconf?                                 no
 393        Does Emacs use GSettings?                               no
 394        Does Emacs use -lselinux?                               no
 395        Does Emacs use -lgnutls?                                yes
 396        Does Emacs use -lxml2?                                  yes
 397        Does Emacs use -lfreetype?                              no
 398        Does Emacs use -lm17n-flt?                              no
 399        Does Emacs use -lotf?                                   no
 400        Does Emacs use -lxft?                                   no
 401        Does Emacs use toolkit scroll bars?                     yes
 402
 403   You are almost there, hang on.
 404
 405   If the output is significantly different, or if configure finishes
 406   prematurely and displays some error message, you should examine the
 407   configuration log in config.log and find the reason for the failure.
 408
 409   Once you succeeded in configuring Emacs, and just want to rebuild it
 410   after updating your local repository from the main repository, you
 411   don't need to re-run the configure script manually, unless you want
 412   to change the configure-time options.  Just typing "make" will
 413   re-run configure if necessary with the exact same options you
 414   specified originally, and then go on to invoking Make, described
 415   below.
 416
 417 * Running Make.
 418
 419   This is simple: just type "make" and sit back, watching the fun.
 420
 421   If you installed a snapshot build of Make, the build will be much
 422   faster if you type "make -j N" instead, where N is the number of
 423   independent processing units on your machine.  E.g., on a core i7
 424   system try using N of 6 or even 8.
 425
 426   When Make finishes, you can install the produced binaries:
 427
 428     make install
 429
 430   or, if you want the installed tree to go in a place different from
 431   the configured one, type
 432
 433     make install prefix=WHEREVER
 434
 435   Congrats!  You have built and installed your own Emacs!
 436
 437 * Make targets
 438
 439   The following make targets may be used by users building the source
 440   distribution, or users who have checked out of Bazaar after
 441   an initial bootstrapping.
 442
 443   make
 444   Builds Emacs from the available sources and pre-compiled lisp files.
 445
 446   make install
 447   Installs the built programs and the auxiliary files.
 448
 449   make clean
 450   Removes object and executable files produced by the build process in
 451   the current configuration.  After "make clean", you can rebuild with
 452   the same configuration using make.  useful when you want to be sure
 453   that all of the products are built from coherent sources.
 454
 455   make distclean
 456   In addition to the files removed by make clean, this also removes
 457   Makefiles and other generated files to get back to the state of a
 458   freshly unpacked source distribution.  After make distclean, it is
 459   necessary to run the configure script followed by "make", in order
 460   to rebuild.
 461
 462   The following targets are intended only for use with the Bazaar sources.
 463
 464   make bootstrap
 465   Removes all the auto-generated files and all the *.elc byte-compiled
 466   files, and builds Emacs from scratch.  Useful when some change in
 467   basic Emacs functionality makes byte compilation of updated files
 468   fail.
 469
 470   make maintainer-clean
 471   Removes everything that can be recreated, including compiled Lisp
 472   files, to get back to the state of a fresh Bazaar tree.  After make
 473   maintainer-clean, it is necessary to run configure and "make" or
 474   "make bootstrap" to rebuild.  Occasionally it may be necessary to
 475   run this target after an update.
 476
 477 * Optional image library support
 478
 479   In addition to its "native" image formats (pbm and xbm), Emacs can
 480   handle other image types: xpm, tiff, gif, png, jpeg and experimental
 481   support for svg.
 482
 483   To build Emacs with support for them, the corresponding headers must
 484   be in the include path and libraries should be where the linker
 485   looks for them, when the configure script is run.  If needed, this
 486   can be set up using the CPPFLAGS and CFLAGS variable specified on
 487   the configure command line.  The configure script will report
 488   whether it was able to detect the headers and libraries.  If the
 489   results of this testing appear to be incorrect, please look for
 490   details in the file config.log: it will show the failed test
 491   programs and compiler error messages that should explain what is
 492   wrong.  (Usually, any such failures happen because some headers are
 493   missing due to bad packaging of the image support libraries.)
 494
 495   Note that any file path passed to the compiler or linker must use
 496   forward slashes, or double each backslash, as that is how Bash
 497   works.
 498
 499   If the configure script finds the necessary headers and libraries,
 500   but they are for some reason incompatible, or if you want to omit
 501   support for some image library that is installed on your system for
 502   some other reason, use the --without-PACKAGE option to configure,
 503   such as --without-gif to omit GIF, --without-tiff to omit TIFF, etc.
 504   Passing the --help option to the configure script displays all of
 505   the supported --without-PACKAGE options.
 506
 507   To use the external image support, the DLLs implementing the
 508   functionality must be found when Emacs first needs them, either on the
 509   PATH, or in the same directory as emacs.exe.  Failure to find a
 510   library is not an error; the associated image format will simply be
 511   unavailable.  Note that once Emacs has determined that a library can
 512   not be found, there's no way to force it to try again, other than
 513   restarting.  See the variable `dynamic-library-alist' to configure the
 514   expected names of the libraries.
 515
 516   Some image libraries have dependencies on one another, or on zlib.
 517   For example, tiff support depends on the jpeg library.  If you did not
 518   compile the libraries yourself, you must make sure that any dependency
 519   is in the PATH or otherwise accessible and that the binaries are
 520   compatible (for example, that they were built with the same compiler).
 521
 522   Binaries for the image libraries (among many others) can be found at
 523   the GnuWin32 project.  PNG, JPEG and TIFF libraries are also
 524   included with GTK, which is installed along with other Free Software
 525   that requires it.  Note specifically that, due to some packaging
 526   snafus in the GnuWin32-supplied image libraries, you will need to
 527   download _source_ packages for some of the libraries in order to get
 528   the header files necessary for building Emacs with image support.
 529
 530   For PNG images, we recommend to use versions 1.4.x and later of
 531   libpng, because previous versions had security issues.  You can find
 532   precompiled libraries and headers on the GTK download page for
 533   Windows (http://www.gtk.org/download/win32.php).
 534
 535   Versions 1.4.0 and later of libpng are binary incompatible with
 536   earlier versions, so Emacs will only look for libpng libraries which
 537   are compatible with the version it was compiled against.  That
 538   version is given by the value of the Lisp variable `libpng-version';
 539   e.g., 10403 means version 1.4.3.  The variable `dynamic-library-alist'
 540   is automatically set to name only those DLL names that are known to
 541   be compatible with the version given by `libpng-version'.  If PNG
 542   support does not work for you even though you have the support DLL
 543   installed, check the name of the installed DLL against
 544   `dynamic-library-alist' and the value of `libpng-version', and
 545   download compatible DLLs if needed.
 546
 547 * Optional GnuTLS support
 548
 549   To compile with GnuTLS, you will need pkg-config to be installed, as
 550   the configure script invokes pkg-config to find out which compiler
 551   switches to use for GnuTLS.  See above for the URL where you can
 552   find pkg-config for Windows.
 553
 554   You will also need to install the p11-kit package, which is a
 555   dependency of GnuTLS, and its header files are needed for
 556   compilation of programs that use GnuTLS.  You can find p11-kit on
 557   the same site as GnuTLS, see the URL below.
 558
 559   If the configure script finds the GnuTLS header files and libraries
 560   on your system, Emacs is built with GnuTLS support by default; to
 561   avoid that you can pass the argument --without-gnutls.
 562
 563   In order to support GnuTLS at runtime, a GnuTLS-enabled Emacs must
 564   be able to find the relevant DLLs during startup; failure to do so
 565   is not an error, but GnuTLS won't be available to the running
 566   session.
 567
 568   You can get pre-built binaries (including any required DLL and the
 569   header files) at http://sourceforge.net/projects/ezwinports/files/.
 570
 571 * Optional libxml2 support
 572
 573   To compile with libxml2, you will need pkg-config to be installed,
 574   as the configure script invokes pkg-config to find out which
 575   compiler switches to use for libxml2.  See above for the URL where
 576   you can find pkg-config for Windows.
 577
 578   If the configure script finds the libxml2 header files and libraries
 579   on your system, Emacs is built with libxml2 support by default; to
 580   avoid that you can pass the argument --without-libxml2.
 581
 582   In order to support libxml2 at runtime, a libxml2-enabled Emacs must
 583   be able to find the relevant DLLs during startup; failure to do so
 584   is not an error, but libxml2 features won't be available to the
 585   running session.
 586
 587   One place where you can get pre-built Windows binaries of libxml2
 588   (including any required DLL and the header files) is here:
 589
 590      http://sourceforge.net/projects/ezwinports/files/
 591
 592   For runtime support of libxml2, you will also need to install the
 593   libiconv "development" tarball, because the libiconv headers need to
 594   be available to the compiler when you compile with libxml2 support.
 595   A MinGW port of libiconv can be found on the MinGW site:
 596
 597    http://sourceforge.net/projects/mingw/files/MinGW/Base/libiconv/
 598
 599   You need the libiconv-X.Y.Z-N-mingw32-dev.tar.lzma tarball from that
 600   site.
 601
 602 * Experimental SVG support
 603
 604   To compile with SVG, you will need pkg-config to be installed, as
 605   the configure script invokes pkg-config to find out which compiler
 606   switches to use for SVG.  See above for the URL where you can find
 607   pkg-config for Windows.
 608
 609   SVG support is currently experimental, and not built by default.
 610   Specify --with-rsvg and ensure you have all the dependencies in your
 611   include path.  Unless you have built a minimalist librsvg yourself
 612   (untested), librsvg depends on a significant chunk of GTK+ to build,
 613   plus a few Gnome libraries, libxml2, libbz2 and zlib at runtime.  The
 614   easiest way to obtain the dependencies required for building is to
 615   download a pre-bundled GTK+ development environment for Windows.
 616
 617   To use librsvg at runtime, ensure that librsvg and its dependencies
 618   are on your PATH.  If you didn't build librsvg yourself, you will
 619   need to check with where you downloaded it from for the
 620   dependencies, as there are different build options.  If it is a
 621   short list, then it most likely only lists the immediate
 622   dependencies of librsvg, but the dependencies themselves have
 623   dependencies - so don't download individual libraries from GTK+,
 624   download and install the whole thing.  If you think you've got all
 625   the dependencies and SVG support is still not working, check your
 626   PATH for other libraries that shadow the ones you downloaded.
 627   Libraries of the same name from different sources may not be
 628   compatible, this problem was encountered with libbzip2 from GnuWin32
 629   with libcroco from gnome.org.
 630
 631   If you can see etc/images/splash.svg, then you have managed to get
 632   SVG support working.  Congratulations for making it through DLL hell
 633   to this point.  You'll probably find that some SVG images crash
 634   Emacs.  Problems have been observed in some images that contain
 635   text, they seem to be a problem in the Windows port of Pango, or
 636   maybe a problem with the way Cairo or librsvg is using it that
 637   doesn't show up on other platforms.
 638
 639 \f
 640 This file is part of GNU Emacs.
 641
 642 GNU Emacs is free software: you can redistribute it and/or modify
 643 it under the terms of the GNU General Public License as published by
 644 the Free Software Foundation, either version 3 of the License, or
 645 (at your option) any later version.
 646
 647 GNU Emacs is distributed in the hope that it will be useful,
 648 but WITHOUT ANY WARRANTY; without even the implied warranty of
 649 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 650 GNU General Public License for more details.
 651
 652 You should have received a copy of the GNU General Public License
 653 along with GNU Emacs.  If not, see <http://www.gnu.org/licenses/>.