[Bf-committers] MSVCR71.DLL

Gilbert, Joseph T. jgilbert at tigr.ORG
Wed Nov 16 22:45:22 CET 2005


Yea it's the python24 dll alright. I ran dependency walker on the
current cvs release target for vc7.1. 
http://tinypic.com/ftlhc4.gif
The python24.dll is calling the msvcr71.dll as it's c runtime library.

-----Original Message-----
From: bf-committers-bounces at projects.blender.org
[mailto:bf-committers-bounces at projects.blender.org] On Behalf Of
Gilbert, Joseph T.
Sent: Wednesday, November 16, 2005 4:22 PM
To: bf-blender developers
Subject: RE: [Bf-committers] MSVCR71.DLL

This would make sense to me. The blender .exe should not be dependant on
the vc7 crt dll (I hope). We need to get someone to build python24.dll
from vc6 and link blender.exe to it and see if it resolves the problem
or not. 

-----Original Message-----
From: bf-committers-bounces at projects.blender.org
[mailto:bf-committers-bounces at projects.blender.org] On Behalf Of Martin
Poirier
Sent: Wednesday, November 16, 2005 3:27 PM
To: bf-blender developers
Subject: Re: [Bf-committers] MSVCR71.DLL



--- Franz Rogar <franzrogar at gmail.com> wrote:

> > > > I'm pretty convinced this file isn't
> nescessary at
> > > all.
> > > Not sure for what it's needed, but some users
> > > reported that it's
> > > needed even to load the program.
> >
> > Don't quote me on this, but I think it comes from
> the
> > Python 2.4 DLL, which is built (officially) with
> MSVC
> > 7.0.
> 
> That's true. The 2.4 branch of Python has the same
> license problem. It
> was discussed in the mailing list about this issue
> and finally, they
> didn't distribute the dll and had to add a nice
> "banner" of license
> saying it was used msvc7...
> 
> > > > It has become a dependancy by either using
> msvc7
> > > > and/or linking with directx headers.
> > > The dependency becomes from using msvc7.
> > >
> > > The msvc6 has no license problems as version 7
> and
> > > can be redistribute
> > > in a more *logical* way.
> >
> > MSVC 6 used to be the "official" environement for
> > building windows release of Blender, IIRC. I don't
> > remember when that changed.
> 
> Some 'testers' use to build against msvc7 because
> they think that
> *last* version seems to be *better* (don't want
> anyone gets ungry).
> License issues are... to drive mad many people. I
> think, my opinion,
> that 'testing' builds (unofficial and official ones)
> should be
> compiled with version 6 *always* to FREE Blender
> from that weird EULA.

I think that DLL will be required for the Python DLL,
regardless of whether or not blender was actually
built with MSVC 7 or not.

We don't really have a choice there, unless we build
our own version of the Python DLL and that's another
big can of worms.

Martin


		
__________________________________ 
Start your day with Yahoo! - Make it your home page! 
http://www.yahoo.com/r/hs
_______________________________________________
Bf-committers mailing list
Bf-committers at projects.blender.org
http://projects.blender.org/mailman/listinfo/bf-committers
_______________________________________________
Bf-committers mailing list
Bf-committers at projects.blender.org
http://projects.blender.org/mailman/listinfo/bf-committers


More information about the Bf-committers mailing list