Am 25.02.2011 09:44, schrieb Hartmut Goebel:
+1
IMHO this would ease debugging: a) If a dll is not on the whitelist it
will not be included and the .exe will not work at all. b) Finding out
there is a dll missing should be easier than finding out there are to
many dlls. c) Since application should not install dlls into \windows
for quite some ears now, this should not be a problem.
Yes, my thoughts exactly. I've written a small patch for bindepend.py
which implements this change as a combined blacklist/whitelist approach.
Bascically the current 'excludes' blacklist is kept but with all the
explicit Windows DLLs removed, and instead the current Windows directory
inserted. Then, a whitelist (I labeled it 'includes') is used to
override certain stuff that would otherwise be excluded (on Windows,
this means currently pythonNN.dll, pythoncomNN.dll and
pywintypesNN.dll). I've run the buildtests and all seems to work as
intended so far. How should I proceed further? Would it be OK to commit
to trunk?
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.
