Some comments on the MSYS-based build

[Óscar Fuentes]

/nt/INSTALL.MSYS says

"A nice GUI installer, called mingw-get,"

mingw-get has no GUI yet. It is a planned feature. However,
mingw-get-inst (confusing, uh?) is a GUI front-end that invokes
mingw-get for MinGW/MSYS installation. It onlyl supports the most
essential packages, though. The URL for mingw-get-inst is:

http://sourceforge.net/projects/mingw/files/Installer/mingw-get-inst/


/nt/INSTALL.MSYS says that mingw-developer-toolkit and msys-automake
should be installed. The mingw-get XML file for mingw-developer-toolkit
says that it includes mingw-automake and the XML file for msys-automake
says:

        <paragraph>This msys port of automake has been modified specifically for
          the MSYS System Builder (msys-dvlpr) environment; that is, it is
          intended to be used only when producing binary packages for the MSYS
          subsystem.  If you intend to produce executables for the native
          "mingw32" subsystem (that is, applications that should work on
          Microsoft Windows installations without the MSYS dll), then you should
          install the mingw32-automake-*, and/or the mingw32-automake1.NN-*
          packages instead.

so it seems that msys-automake is unnecesary.


MSYS has its own top-level configure script (/nt/msysconfig.sh) Shall we
expect from it the same features than from /confgiure.sh? (modulo OS
differences) For instance, /INSTALL mentions

`GZIP_PROG' is the name of the executable that compresses installed info,
        manual, and .el files.  It defaults to gzip.  Setting it to
        the empty string suppresses compression.

and my build script has

    export GZIP_PROG=""  # Do not compress .elc files
    if ! ../emacs/nt/msysconfig.sh --prefix $einstall ; then
        exit 12
    fi

but the build compresses the .el files.