You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by "Pedro F. Giffuni via dev" <de...@openoffice.apache.org> on 2026/07/26 17:21:50 UTC
Fw: python and newer MSVC versions
Hello;Haven't been following a lot lately, but if you are still trying to build AOO's Python 2.7.x with MSVC2011, then this still applies.If you moved on to Python 3.X nevermind ... that's its own can of worms :).
Cheers,
Pedro.
----- Forwarded Message ----- From: Pedro F. GiffuniTo: dev@openoffice.apache.orgSent: Saturday, February 14, 2026 at 01:06:49 AM GMT-5Subject: Re: python and newer MSVC versions
Hello;
Sorry to bring this up again, with the greatest respect to Damjan's work to get this building somehow. The following patches are wrong and should be removed:
main/python/python-2.7.18-msvs9-win64-target.patch
main/python/python-2.7.18-msvs9-win64.patch
Microsoft Visual C++ 9.0 (AKA Visual Studio 2008) doesn't support Win64, and the path is specifically meant for that compiler.
Python 2.x still support the old compiler on misc/build/Python-2.7.18/PC/VS9.0
but newer compilers should be using misc/build/Python-2.7.18/PCBuild
Fixing that for newer compilers should make things a lot easier.
Congratulations everybody, specially Damjan for the hard work and the the amd64 nearing!
Pedro.
On Friday, February 28, 2025 at 10:50:23 AM GMT-5, Pedro F. Giffuni wrote:
Hi;
As a follow up to my comments on python and MSVC versions, I think a starting point to fix the build problem correctly would be to add something like this in main/python/makefile.mk (around line 127)
# Requires adapting for according to the MSVC compiler version.# Normally PCBuild will carry the latest supported build files..IF "$(CCNUMVER)" <= "00150030729"BUILD_DIR=PC/VS9.0.ELSEBUILD_DIR=PCBuild.ENDIF
_____
There is no VS/10.0, at least not for python 2.7.x, as I had thought previously, and we shouldn't worry about any MS Visual C++ older than 2008.
Yes, I realize this involves boring rework, but that's the way the python documentation suggests.
Cheers,
Pedro.
* The numering is based on:https://en.wikipedia.org/wiki/Microsoft_Visual_C%2B%2B
Re: Fw: python and newer MSVC versions
Posted by Pe...@apache.org.
Hi Pedro,
At least on bazel-migration branch, the patches do not exist anymore. I
am not sure if we need those patches or do they fix something.
My standpoint is it works perfectly nice now, after 2 additional fixes
in the bridge. I am still on it to get trunk build again. Then we might
see a different behavior. don't know.
All the best
Peter
Am 26.07.2026 um 19:21 schrieb Pedro F. Giffuni via dev:
> Hello;Haven't been following a lot lately, but if you are still trying to build AOO's Python 2.7.x with MSVC2011, then this still applies.If you moved on to Python 3.X nevermind ... that's its own can of worms :).
> Cheers,
> Pedro.
> ----- Forwarded Message ----- From: Pedro F. GiffuniTo: dev@openoffice.apache.orgSent: Saturday, February 14, 2026 at 01:06:49 AM GMT-5Subject: Re: python and newer MSVC versions
> Hello;
> Sorry to bring this up again, with the greatest respect to Damjan's work to get this building somehow. The following patches are wrong and should be removed:
> main/python/python-2.7.18-msvs9-win64-target.patch
> main/python/python-2.7.18-msvs9-win64.patch
>
> Microsoft Visual C++ 9.0 (AKA Visual Studio 2008) doesn't support Win64, and the path is specifically meant for that compiler.
> Python 2.x still support the old compiler on misc/build/Python-2.7.18/PC/VS9.0
> but newer compilers should be using misc/build/Python-2.7.18/PCBuild
> Fixing that for newer compilers should make things a lot easier.
> Congratulations everybody, specially Damjan for the hard work and the the amd64 nearing!
> Pedro.
> On Friday, February 28, 2025 at 10:50:23 AM GMT-5, Pedro F. Giffuni wrote:
>
> Hi;
> As a follow up to my comments on python and MSVC versions, I think a starting point to fix the build problem correctly would be to add something like this in main/python/makefile.mk (around line 127)
> # Requires adapting for according to the MSVC compiler version.# Normally PCBuild will carry the latest supported build files..IF "$(CCNUMVER)" <= "00150030729"BUILD_DIR=PC/VS9.0.ELSEBUILD_DIR=PCBuild.ENDIF
> _____
> There is no VS/10.0, at least not for python 2.7.x, as I had thought previously, and we shouldn't worry about any MS Visual C++ older than 2008.
> Yes, I realize this involves boring rework, but that's the way the python documentation suggests.
> Cheers,
> Pedro.
> * The numering is based on:https://en.wikipedia.org/wiki/Microsoft_Visual_C%2B%2B
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Fw: python and newer MSVC versions
Posted by Pe...@apache.org.
Hi Pedro,
Am 26.07.2026 um 19:21 schrieb Pedro F. Giffuni via dev:
> Hello;Haven't been following a lot lately, but if you are still trying to build AOO's Python 2.7.x with MSVC2011, then this still applies.If you moved on to Python 3.X nevermind ... that's its own can of worms :).
Good point. I forgot about the mail. Thanks for the bumb.
> Cheers,
> Pedro.
> ----- Forwarded Message ----- From: Pedro F. GiffuniTo: dev@openoffice.apache.orgSent: Saturday, February 14, 2026 at 01:06:49 AM GMT-5Subject: Re: python and newer MSVC versions
> Hello;
> Sorry to bring this up again, with the greatest respect to Damjan's work to get this building somehow. The following patches are wrong and should be removed:
> main/python/python-2.7.18-msvs9-win64-target.patch
> main/python/python-2.7.18-msvs9-win64.patch
>
> Microsoft Visual C++ 9.0 (AKA Visual Studio 2008) doesn't support Win64, and the path is specifically meant for that compiler.
> Python 2.x still support the old compiler on misc/build/Python-2.7.18/PC/VS9.0
> but newer compilers should be using misc/build/Python-2.7.18/PCBuild
> Fixing that for newer compilers should make things a lot easier.
> Congratulations everybody, specially Damjan for the hard work and the the amd64 nearing!
> Pedro.
> On Friday, February 28, 2025 at 10:50:23 AM GMT-5, Pedro F. Giffuni wrote:
>
> Hi;
> As a follow up to my comments on python and MSVC versions, I think a starting point to fix the build problem correctly would be to add something like this in main/python/makefile.mk (around line 127)
> # Requires adapting for according to the MSVC compiler version.# Normally PCBuild will carry the latest supported build files..IF "$(CCNUMVER)" <= "00150030729"BUILD_DIR=PC/VS9.0.ELSEBUILD_DIR=PCBuild.ENDIF
> _____
> There is no VS/10.0, at least not for python 2.7.x, as I had thought previously, and we shouldn't worry about any MS Visual C++ older than 2008.
> Yes, I realize this involves boring rework, but that's the way the python documentation suggests.
> Cheers,
> Pedro.
> * The numering is based on:https://en.wikipedia.org/wiki/Microsoft_Visual_C%2B%2B
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org