Am 24.02.2011 19:29, schrieb Michael Durian:
On Feb 24, 2011, at 11:25 AM, Florian Höch wrote:
Am 24.02.2011 19:01, schrieb Michael Durian:
On Feb 24, 2011, at 10:34 AM, Florian Höch wrote:
Hi,
Am 24.02.2011 16:57, schrieb Michael Durian:
I've gone ahead and installed python and the dependancies I
need under XP so I can run PyInstaller on it. I just used
ArchiveViewer.py to compare the .exe generated under XP to
the one generated under Windows 7. Aside from some offset
differences starting with irprops.cpl, the XP build does
include some files not found in the Windows 7 build.
Specifically, DEVMGR.DLL SETUPAPI.dll WMI.dll
Those look a lot like system DLLs to me. It could actually be
necessary to add those to PyInstaller's exclude list. Does the
executable generated in XP run in Windows 7?
Yes, it does.
If those system DLLs are present in the XP build, which runs on
XP and W7, how would adding them to an exclude list allow a build
on W7 to run on XP?
No, the other way around. If the XP build would fail on W7, then
adding those DLLs to the exclude list may have helped
What do I need to do to get them included in a W7 build? I tried
adding them to hiddenimports, but that didn't work. How do you
specify a list of additional DLLs that need to be included in the
build?
Do they even exist on W7? You could do a search in Windows\system32.
Another possibility could be that PyBluez actually installs different
files with different dependencies on W7 and XP. This would not be easy
to fix I think.
Regards
--
Florian Höch
--
You received this message because you are subscribed to the Google Groups
"PyInstaller" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pyinstaller?hl=en.
