Le Mon, 23 Jul 2018 10:47:33 -0700,
Nathaniel Smith a écrit :
> On Mon, Jul 23, 2018, 08:22 Eric Le Lay wrote:
>
> > Hello list,
> >
> > I encountered a problem with the Windows packaging of gPodder[1]
> > using msys2:
> >
> > basic libraries (zlib, openssl) depended upon by python
> >
MSYS2 has two Python ports, msys2 and mingw-w64. I believe Eric was
referring to the mingw-w64 one?
zlib1.dll in C:\Windows\System32 is a packaging error on the part of
whatever put it there and that is what needs to be fixed here. ISVs
need to stop putting anything in that directory as it leads
On Mon, Jul 23, 2018 at 2:31 PM, Eric Le Lay wrote:
>
> I encountered a problem with the Windows packaging of gPodder[1]
> using msys2:
Are you using regular Windows Python with msys2, or their custom port?
I installed msys2 and used pacman to install Python 3.6. The msys2
environment names
On Mon, Jul 23, 2018, 08:22 Eric Le Lay wrote:
> Hello list,
>
> I encountered a problem with the Windows packaging of gPodder[1]
> using msys2:
>
> basic libraries (zlib, openssl) depended upon by python
> platform-specific modules are loaded preferably :
> 1. from lib-dynload (where they are
In general, if the dependent DLL is in the same directory as the module
loading it (the .pyd or .exe), then it should be loaded first. If it's
alongside the .exe, it should be loaded before any of the other search
paths. If it's being loaded directly from Python, your best option is to
resolve
Hello list,
I encountered a problem with the Windows packaging of gPodder[1]
using msys2:
basic libraries (zlib, openssl) depended upon by python
platform-specific modules are loaded preferably :
1. from lib-dynload (where they are not)
2. from the Windows directory (can be any version)
3.
