|
From: Massa, H. A. <ch...@gh...> - 2020-04-13 20:38:17
|
Hi Jeffrey,
> Besides py2exe seemingly embedding its signature into python27.dll, here
> are a few other oddities.
> The good build copies API-MS-Win-Core-LocalRegistry-L1-1-0.dll. I don't
> think it should do this.
> The bad version does not copy this file.
> The bad version copies bcrypt.dll and crypt32.dll, the good version does
> not.
> The produced executables also do not match.
>
cannot explain anything about the py2exe signature in python27.dll. But the
"API-MS-Win-Core..." and the bcrypt.dll and crypt32.dll problem I have
experienced intensely.
So, in my setup-scripts the following things are pushed into dll_excludes:
"dll_excludes": ["tk84.dll", "tcl84.dll", "_tkinter.pyd", "_imagingtk.pyd",
"w9xpopen.exe", 'msvcr71.dll', 'win32ui.pyd',
"MSVCP90.dll",
# starting with Windows 7
"kernelbase.dll", "mpr.dll",
"powrprof.dll", "secur32.dll",
"shfolder.dll",
"API-MS-Win-Core-LocalRegistry-L1-1-0.dll",
"API-MS-Win-Core-ProcessThreads-L1-1-0.dll",
"API-MS-Win-Security-Base-L1-1-0.dll",
# starting with Windows 10
"CRYPT32.dll",
"bcrypt.dll",
]
Beginning only valid as I do not want to use tkinter.
The things starting at "windows 7" - if I do not exclude those dll, the
distribution does not work.
So, my recommendation: Try to exclude those dlls.
(and, by chance, are your builds on different windows versions?)
Cheers
Harald
--
GHUM GmbH
Harald Armin Massa
Spielberger Straße 49
70435 Stuttgart
0173/9409607
Amtsgericht Stuttgart, HRB 734971
|