Message257879
Binaries created by bdist_wininst fail on 3.5+ for 2 reasons:
* The built binary links against the DLL version of the CRT. This means the binary will typically fail to start as the CRT DLL isn't found.
* When looking for 32bit Python versions, it fails to take the recent "-32" change for the registry key, so it tells you no Python is installed.
This patch:
* Uses the static CRT, which IIRC, was the case in previous Python versions.
* Changes directory to the directory with pythonxx.dll before attempting to loadlibrary it - this allows the loadlibrary to succeed as the CRT DLL in that directory is found.
* Appends "-32" to registry keys on 32bit builds.
With these patches I can successfully get a pywin32 build working and installing.
Steve (or anyone), what do you think?
(Note that the attached patch does *not* include a newly built wininst-14.exe, but that would obviously need to be updated before checking in.) |
|
Date |
User |
Action |
Args |
2016-01-10 01:06:48 | mhammond | set | recipients:
+ mhammond, paul.moore, tim.golden, zach.ware, steve.dower |
2016-01-10 01:06:48 | mhammond | set | messageid: <1452388008.63.0.0329055331541.issue26071@psf.upfronthosting.co.za> |
2016-01-10 01:06:48 | mhammond | link | issue26071 messages |
2016-01-10 01:06:48 | mhammond | create | |
|