Back on 8-Feb-05,
"Martin v. Löwis"
martin at v.loewis.de said:
>> "An application should use and
redistribute msvcr71.dll, and it should>> avoid placing a copy
or using an existing copy of msvcr71.dll in the>> system
directory. Instead, the application should keep a copy of>>
msvcr71.d
Matthias Baas wrote:
I'm creating the installer via the distutils by calling "setup.py
bdist_wininst". How can I configure distutils to have it create an
installer that does the above things?
Ah, I see. Unfortunately, bdist_wininst is not capable of doing
a Windows logo compliant installation (with
On Tue, 01 Feb 2005 00:14:30 +0100, "Martin v. Löwis"
<[EMAIL PROTECTED]> wrote:
>> are there any guidelines about what to do if a Windows extension for
>> Python 2.4 requires the C++ runtime (msvcp71.dll)?
>
>No; it should "just work fine". [...]
I fully agree with that. :) And that was actuall
Matthias Baas wrote:
are there any guidelines about what to do if a Windows extension for
Python 2.4 requires the C++ runtime (msvcp71.dll)?
No; it should "just work fine". The standard guidelines apply, of
course: never try to mix different versions of similar DLLs.
If I want to
distribute a bin
Hi,
are there any guidelines about what to do if a Windows extension for
Python 2.4 requires the C++ runtime (msvcp71.dll)? If I want to
distribute a binary installer of an extension that contains C++ code,
should I really include the msvcp71.dll in the package? It doesn't
sound like a good idea
