Re: [python-win32] More info about Microsoft Foundation Classes (MFC)

[Tim Roberts]

Thomas Pietrowski wrote:
> Ok, so basically the same I know from Linux.
> But how likely is it that Python 2.7.14 (which is currently the latest
> version) is linked against old libraries?
> Isn't the Python Foundation updating their build system regularly, too?

No.  In the past, the policy has been whatever build system is used for
2.7.0 will be used for all 2.7.x releases.  If they upgrade their Visual
Studio, then all users have to upgrade, too, and in the Windows world
that costs money.


> At the moment I'm quite convinced that the choice of an MFC version
> does not depend on Python, but on which version you built PyWin32.
> However, this is only my current feeling.

Right.  The core interpreter has no UI, and does not link to MFC.

-- 
Tim Roberts, t...@probo.com
Providenza & Boekelheide, Inc.

___
python-win32 mailing list
python-win32@python.org
https://mail.python.org/mailman/listinfo/python-win32

Re: [python-win32] More info about Microsoft Foundation Classes (MFC)

[Thomas Pietrowski]

Ok, so basically the same I know from Linux.
But how likely is it that Python 2.7.14 (which is currently the latest
version) is linked against old libraries?
Isn't the Python Foundation updating their build system regularly, too?

At the moment I'm quite convinced that the choice of an MFC version does
not depend on Python, but on which version you built PyWin32.
However, this is only my current feeling.

Is our test script able to check a breakage here? So I would know by tests,
whether it is safe to take newer MFC libraries or not?



2018-03-29 19:15 GMT+02:00 Tim Roberts :

> Thomas Pietrowski wrote:
> >
> > I have general questions about MFC and hope you can answer them.
> > When compiling PyWin32 for Py2.7 and Py3.x I get successful builds,
> > but setup.py can't find the MFC libraries,
> > which are specified here:
> > https://github.com/thopiekar/pywin32/blob/master/setup.py#L1059
> > for Python 2.7, Python 3.3 and Python3.4. This happens while using
> > Appveyor and I contacted them about these "missing" files.
> > One of the developers contacted me back and asked, whether mfc90*.dll
> > is really needed for Python2.7.
> > I think the question is quite eligible: Why are exactly these versions
> > of MFC libraries strictly specified here?
> > Isn't it possible to take the latest version, which is available?
> > (Which is there for Python3.5 and 3.6.)
>
> No.  It may not be obvious, but Python itself it entirely implemented in
> a DLL.  (Note that the "python.exe" command is only a couple dozen
> kilobytes.)  That DLL links to the dynamic version of the C run-time
> library.  To avoid conflicts in shared state and such, all of the DLLs
> it calls must either use a static C run-time library, or the same
> dynamic version that Python itself uses.  The same applies to MFC.  When
> an application or DLL links with MFC, it links to a specific version
> (e.g., mfc90.dll).  You can't substitute another.
>
> --
> Tim Roberts, t...@probo.com
> Providenza & Boekelheide, Inc.
>
> ___
> python-win32 mailing list
> python-win32@python.org
> https://mail.python.org/mailman/listinfo/python-win32
>
___
python-win32 mailing list
python-win32@python.org
https://mail.python.org/mailman/listinfo/python-win32

Re: [python-win32] More info about Microsoft Foundation Classes (MFC)

[Tim Roberts]

Thomas Pietrowski wrote:
>
> I have general questions about MFC and hope you can answer them.
> When compiling PyWin32 for Py2.7 and Py3.x I get successful builds,
> but setup.py can't find the MFC libraries,
> which are specified here:
> https://github.com/thopiekar/pywin32/blob/master/setup.py#L1059
> for Python 2.7, Python 3.3 and Python3.4. This happens while using
> Appveyor and I contacted them about these "missing" files.
> One of the developers contacted me back and asked, whether mfc90*.dll
> is really needed for Python2.7.
> I think the question is quite eligible: Why are exactly these versions
> of MFC libraries strictly specified here?
> Isn't it possible to take the latest version, which is available?
> (Which is there for Python3.5 and 3.6.)

No.  It may not be obvious, but Python itself it entirely implemented in
a DLL.  (Note that the "python.exe" command is only a couple dozen
kilobytes.)  That DLL links to the dynamic version of the C run-time
library.  To avoid conflicts in shared state and such, all of the DLLs
it calls must either use a static C run-time library, or the same
dynamic version that Python itself uses.  The same applies to MFC.  When
an application or DLL links with MFC, it links to a specific version
(e.g., mfc90.dll).  You can't substitute another.

-- 
Tim Roberts, t...@probo.com
Providenza & Boekelheide, Inc.

___
python-win32 mailing list
python-win32@python.org
https://mail.python.org/mailman/listinfo/python-win32

[python-win32] More info about Microsoft Foundation Classes (MFC)

[Thomas Pietrowski]

Hey,

I have general questions about MFC and hope you can answer them.
When compiling PyWin32 for Py2.7 and Py3.x I get successful builds, but
setup.py can't find the MFC libraries,
which are specified here:
https://github.com/thopiekar/pywin32/blob/master/setup.py#L1059
for Python 2.7, Python 3.3 and Python3.4. This happens while using Appveyor
and I contacted them about these "missing" files.
One of the developers contacted me back and asked, whether mfc90*.dll is
really needed for Python2.7.
I think the question is quite eligible: Why are exactly these versions of
MFC libraries strictly specified here?
Isn't it possible to take the latest version, which is available? (Which is
there for Python3.5 and 3.6.)

Hope someone can explain so I can understand and find a solution for it, so
we can build everything on Appveyor.

Regards!
___
python-win32 mailing list
python-win32@python.org
https://mail.python.org/mailman/listinfo/python-win32