1 This is the plan for building Python under the MinGW Windows
2 cross-compiler -- Richard W.M. Jones (rjones@redhat.com) 2008-12-11.
3 ----------------------------------------------------------------------
5 Originally we had envisaged only building Python 3. However because
6 Python 3 is substantially incompatible with existing Python code and
7 Python bindings to C libraries, this would have made this project less
8 than useful for current Python code.
10 The current plan is to maintain two sets of patches, to Python 2.6 and
11 Python 3.x, keeping the patches as similar as possible, and getting
12 them upstream quickly. This allows code to continue to be Python 2.x
13 compatible, while providing an upgrade path to Python 3, and providing
14 a reasonable way to get patches upstream and experiment with the
15 bleeding edge Python 3.
17 Note that Python 3 is not yet in Fedora, but we require a native
18 Python binary is available in order to compile (otherwise the
19 generated python.exe has to be run during the compile, but there are
20 numerous problems with doing that in practice). Thus in order to
21 build mingw32-python3, we also have to build our own native python3
22 "compatibility package" if you will. This is completely different
23 from whatever Fedora will decide to do in future, and is not to be
24 confused with the real Python 3 for Fedora. Once real Python 3 exists
25 in Fedora, we can drop this compatibility package.
27 In conclusion, the packages we are building are:
29 In python/ subdirectory:
31 mingw32-python Python 2.6 cross-compiled to Windows.
33 In python3/ subdirectory:
35 mingw32-python3 Python 3.x cross-compiled to Windows.
37 python3 Fake Python 3 native package (we don't
38 intend to ever release this, beyond
43 ----------------------------------------------------------------------
45 mingw32-python (cross-compiled Python 2.6): Initial build. Contains
46 no Fedora native patches yet.
48 mingw32-python3: Initial build.
50 python3: Fake package created.