Re: building Emacs on Msys2/mingw32

[Chris Zheng]

From: Stephen Leake <address@hidden>
Subject: Re: building Emacs on Msys2/mingw32
Date: Tue, 09 Sep 2014 00:00:29 -0500

Hi Stephen,
> Sigh. I was actually running mingw64_shell.bat, not msys2_shell.bat. I
> just got the wrong name in the emails. Thanks for catching this.
> 
> However, Emacs configure was run under Emacs, not directly in the
> mingw64 shell, which means I was trying to emulate mingw64_shell.bat
> with elisp code. So I need to figure out what I got wrong in that
> emulation. I don't see anything obvious in the shell/environment
> variables. 
Sorry, I can't follow the hole discussion.  But if you want to run
./configure under Emacs, say, the in shell-mode, you can add
  export MSYSTEM=MINGW64
to ~/.bashrc, this will complete what mingw64_shell.bat do for the
build.  And this is what I have done.
> On the gripping hand, I just tested configure under mingw64_shell.bat,
> and got:
> 
> configure: error: Emacs does not support `x86_64-pc-mingw64'. 
> 
> Which is fine; we need i686.
> 
> So I tried mingw32_shell.bat; that works.
> 
> Just to be clear, the default prefix is still /usr/local. But /usr
> exists in msys2/mingw32; it is at c:/msys64/usr. So /usr/local is a
> reasonable place to install emacs. Except that will mix 32 bit and 64
> bit targets; /usr/local/x86_64 and /usr/local/i686 would be better. So I
> suggest we keep the advice to specify --prefix.
I personal prefer /mingw32/local and /mingw64/local because: (1) The
/usr is for MSYS2 system, and programs in it will depend on
msys-*.dll, like Cygwin does.  But Emacs was native Windows programs
which doesn't not depend on MSYS2 dlls; (2) /mingw32 and /mingw64 are
unique and don't exist in /usr and other paths; (3) The Emacs you
builded are more likely a MinGW32 or MinGW64 program than a MSYS2
program, so it should come to /mingw32 or /mingw64.

Best wishes,
Chris.