Hi Glenn, I'm glad you have asked.
Last week I was working on Python3 support for windows in my branch: https://github.com/matysek/pyinstaller/tree/modulegraph And I fixed there similar issue: - python 3.3+ depends on msvc100 dlls - python 2.7, 3.0, 3.1, 3.2 depends on msvc90 dlls - msvc90 dlls require SxS manifest - msvc100 dlls no longer require SxS manifest - msvc100 dlls are put into C:\Windows\System32 - pyinstaller by default ignores all files from C:\Windows\System32 - I had to explicitly tell pyinstaller to bundle msvc100 dlls How to fix it for development branch: - look at file ./PyInstaller/depend/dylib.py and use similar fix for the pyinstaller development branch. On Monday 09 of June 2014 17:12:51 Glenn Ramsey wrote: > Hi, > > I have a project that has several Boost.Python modules built on Windows > using VS2010. These modules depend on the MSVC100* dlls. PyInstaller > (current develop branch, dir mode) is not packaging these dlls. It does > package the MSVC90* dlls that python27.dll depends on. > > Running utils/bindepend.py on the modules does find the dependencies on the > MSVC100* dlls. I don't see anything obvious in the debug output when running > PyInstaller. > > This project was working with a previous development build of PyInstaller > but I'm not sure when this error started happening. > > Is there a way I can make PyInstaller package these dlls? > > Glenn
signature.asc
Description: This is a digitally signed message part.
