Re: [Py2exe-users] Re: msvcr71.dll license

[RayS <ra...@bl...>]

At 05:27 AM 5/20/2005, Werner F. Bruhin wrote:
>>Hence, py2exe users need a legit copy of VS and to write an
>>EULA compatible license and to implement a way for approval
>>if they want to include msvcr71.dll in their package. (*)

I have not been including it for the reason of package size; if a user does not have it, they can download it from a variety of places - presumably legally:
http://www.dll-files.com/dllindex/pop.php?msvcr71

http://www.dlldump.com/cgi-bin/testwrap/downloadcounts.cgi?rt=count&path=dllfiles/M/MSVCR71.dll

Office update contains the dll:
http://www.microsoft.com/downloads/info.aspx?na=90&p=&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=d21f3d89-46ac-4a27-b4c7-be05723d53e5&genscs=&u=http%3a%2f%2fdownload.microsoft.com%2fdownload%2fb%2f4%2f3%2fb43fab6b-862a-4371-ab31-0f8e681f8e28%2fBusinessContactManager-kb839881-fullfile-enu.exe

I would assume that there is no restriction on distributing software that simply requires it... I suppose you could trap for it, automatically alert the user and start a download with os.startfile()
OTOH, if you sent CDs, it is more of an issue.


>AFAIK, GPL code cannot be linked with closed source dlls not included with the operating system. Or something like that.

Also, from MS:
http://support.microsoft.com/default.aspx?scid=kb;en-us;326922
" the Msvcr71.dll/Msvcr70.dll is no longer considered a system file, therefore, distribute Msvcr71.dll/Msvcr70.dll with any application that relies on it. Because it is no longer a system component, install it in your applications Program Files directory with other application-specific code. This prevents your application from using other versions of the CRT library that may be installed on the system paths.
When you distribute applications that require the Msvcr71.dll/Msvcr70.dll Shared CRT library, Microsoft recommends that you use the VC_CRT.msm merge module that is included with with Visual C++ .NET instead of directly distributing the DLL file. "
So installers/users may want to take heed.

>One might say that py2exe users don't split the Python interpreter
>but include it as a whole.  

Which I would agree with; in my view "splitting" the core interpreter simply causes it not not run - the only other alternative is to include an entire Python install on the distribution CD, which is then prohibitive to download-only users.

>While this point might be a matter of
>opinion (*) there's no doubt that they *must at least* provide their
>end-users a way to "sign" the Python Software License, an action
>demanded by Microsoft's EULA.

Good point, I should see that it is added to the usual Inno Setup verbiage.

Ray Schumacher