[PATCH 2 of 2 STABLE] setup: search for proper library name on MinGW/msys2
Adrian Buehlmann
adrian at cadifra.com
Wed Apr 27 08:50:30 EDT 2016
On 2016-04-27 01:36, Gregory Szorc wrote:
> On Tue, Apr 26, 2016 at 4:25 PM, Gregory Szorc <gregory.szorc at gmail.com
> <mailto:gregory.szorc at gmail.com>> wrote:
>
> # HG changeset patch
> # User Gregory Szorc <gregory.szorc at gmail.com
> <mailto:gregory.szorc at gmail.com>>
> # Date 1461712815 25200
> # Tue Apr 26 16:20:15 2016 -0700
> # Branch stable
> # Node ID a42a7f71b89a026572f8ce798fa2c2bbaf6dea3a
> # Parent ba89075c616d56c3f1ce02c97103c6d0ff8aa006
> setup: search for proper library name on MinGW/msys2
>
>
> Give the lateness in the release cycle, I'd feel a lot better about this
> if other Windows packagers weighed in.
>
> We discovered this issue at Mozilla as part of trying to make Firefox
> build with msys2 rather than our hacked together msys1-based environment
> (which contains the official Windows Python distribution instead of the
> msys one). With this patch, `pip install Mercurial` "just works" under
> msys2/MinGW and doesn't produce a useless hg.exe.
I started exewrapper.c mainly for being able to run more tests of the
testsuite on Windows.
I think Steve doesn't use it for the hg.exe that he's building for the
*.msi packages for Windows. I think he uses py2exe for that, which puts
the python modules into a library.zip.
So I believe your changes to exewrapper.c are unlikely to affect Steve.
More information about the Mercurial-devel
mailing list