From: Markus Gritsch <gritsch@iu...> - 2005-09-08 20:31:52
In former, for deploying my app I had to add msvcr71.dll and msvcp71.dll via the
data_files parameter of the setup() function.
py2exe 0.6.2 adds MSVCR71.dll to the dist directory automatically. It would be
nice, if MSVCP71.dll would also be added automatically.
From: Thomas Heller <theller@py...> - 2005-09-16 15:02:23
Markus Gritsch <gritsch@...> writes:
> In former, for deploying my app I had to add msvcr71.dll and msvcp71.dll via the
> data_files parameter of the setup() function.
> py2exe 0.6.2 adds MSVCR71.dll to the dist directory automatically. It would be
> nice, if MSVCP71.dll would also be added automatically.
> Kind regards,
Hi Marcus, I intent to change the 'policy' in py2exe anyway. Currently,
py2exe uses the image base address of a dll to determine of this is a
'system dll' or not (system dlls are NOT copied to dist, non-system dlls
are copied). I read in some MS docs about the load address.
Unfortunately, this mechanism does not relly work, so py2exe has an
additional list of dlls the are never copied (msvcrt.dll is an example).
The 0.6.2 release added an additional rule for msvcr71.dll - it IS
copied if found to be needed.
For a future release (but probably not 0.6.3) I want to change the
policy to these rules:
- if the dll is in the windows system directory it will not be copied,
except for some special dlls which are known to be non-system dlls
- if the dll is in another directory it will be copied.
Hopefully that works better. To override these rules in cases they
don't work correctly, it may be needed to add additional parameters to
- A way to specify dlls that should not be copied to the dist directory.
This is already present but little known - dll_excludes.
- A way to specify dlls that should be copied to the dist directory (not
- And finally, for the bundle_files option, a way to specify which dlls
should be bundled into the exe and which dlls should NOT be bundled into