[reopening] native build of python win32 using msys under both wine and native win32

[lkcl]

BPO	5026
Files	f x: manifests and rc files

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2010-06-26.00:03:04.568>
created_at = <Date 2009-01-21.19:08:12.292>
labels = ['build']
title = '[reopening] native build of python win32 using msys under both wine and native win32'
updated_at = <Date 2010-06-26.00:03:04.566>
user = 'https://bugs.python.org/lkcl'

bugs.python.org fields:

activity = <Date 2010-06-26.00:03:04.566>
actor = 'terry.reedy'
assignee = 'none'
closed = True
closed_date = <Date 2010-06-26.00:03:04.568>
closer = 'terry.reedy'
components = ['Build']
creation = <Date 2009-01-21.19:08:12.292>
creator = 'lkcl'
dependencies = []
files = ['12827', '12829']
hgrepos = []
issue_num = 5026
keywords = []
message_count = 5.0
messages = ['80339', '80340', '80342', '80345', '80485']
nosy_count = 1.0
nosy_names = ['lkcl']
pr_nums = []
priority = 'normal'
resolution = 'out of date'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue5026'
versions = ['Python 2.5']

[lkcl]

reopening a new bug with the exact same title due to bpo-4954 having
been unilaterally closed without discussion, nor reasons specified.

simple courtesy would dictate that some sort of dialog is entered
into especially when someone is putting in significant amounts of
work in developing python, and has plans to forward-port the patch
to python2.6 and trunk, merge it with bpo-3844 and much more.

[lkcl]

so.

let me be clear.

this bug is a continuation of work to port python to mingw,
with a specific BUT NOT UNIQUE focus of ensuring that python
can be compiled under wine.

THE ATTACHED PATCH CAN ALSO BE USED TO COMPILE PYTHON UNDER WIN32.

[lkcl]

attached also manifests and rc files for building on msvcr80

[lkcl]

martin - apologies for shouting: i hadn't seen your explanations
of why bpo-4954 was closed. i'm not happy that it _was_ closed, but
that's another story.

yes of course i will be going on to python2.6 and up - first though
is to focus on python2.5 and get _that_ into shape, then moving
on to 2.6 and 2.7 is easy.

[lkcl]

bpo-5046 supercedes this patch, for python2.7. still relevant
for python2.5 though.