@@ -268,13 +268,13 @@ file winds up deep in the "build tree," in a temporary directory created by
268268.. % \longprogramopt{spec-file} option; used in conjunction with
269269.. % \longprogramopt{spec-only}, this gives you an opportunity to customize
270270.. % the \file{.spec} file manually:
271- .. %
271+ .. %
272272.. % \ begin{verbatim}
273273.. % > python setup.py bdist_rpm --spec-only
274274.. % # ...edit dist/FooBar-1.0.spec
275275.. % > python setup.py bdist_rpm --spec-file=dist/FooBar-1.0.spec
276276.. % \ end{verbatim}
277- .. %
277+ .. %
278278.. % (Although a better way to do this is probably to override the standard
279279.. % \command{bdist\_rpm} command with one that writes whatever else you want
280280.. % to the \file{.spec} file.)
@@ -334,31 +334,31 @@ The installer file will be written to the "distribution directory" --- normally
334334Cross-compiling on Windows
335335==========================
336336
337- Starting with Python 2.6, distutils is capable of cross-compiling between
338- Windows platforms. In practice, this means that with the correct tools
337+ Starting with Python 2.6, distutils is capable of cross-compiling between
338+ Windows platforms. In practice, this means that with the correct tools
339339installed, you can use a 32bit version of Windows to create 64bit extensions
340340and vice-versa.
341341
342- To build for an alternate platform, specify the :option: `--plat-name ` option
343- to the build command. Valid values are currently 'win32', 'win-amd64' and
342+ To build for an alternate platform, specify the :option: `--plat-name ` option
343+ to the build command. Valid values are currently 'win32', 'win-amd64' and
344344'win-ia64'. For example, on a 32bit version of Windows, you could execute::
345345
346346 python setup.py build --plat-name=win-amd64
347347
348- to build a 64bit version of your extension. The Windows Installers also
348+ to build a 64bit version of your extension. The Windows Installers also
349349support this option, so the command::
350350
351351 python setup.py build --plat-name=win-amd64 bdist_wininst
352352
353353would create a 64bit installation executable on your 32bit version of Windows.
354354
355- To cross-compile, you must download the Python source code and cross-compile
355+ To cross-compile, you must download the Python source code and cross-compile
356356Python itself for the platform you are targetting - it is not possible from a
357357binary installtion of Python (as the .lib etc file for other platforms are
358- not included.) In practice, this means the user of a 32 bit operating
359- system will need to use Visual Studio 2008 to open the
360- :file: `PCBuild/PCbuild.sln ` solution in the Python source tree and build the
361- "x64" configuration of the 'pythoncore' project before cross-compiling
358+ not included.) In practice, this means the user of a 32 bit operating
359+ system will need to use Visual Studio 2008 to open the
360+ :file: `PCBuild/PCbuild.sln ` solution in the Python source tree and build the
361+ "x64" configuration of the 'pythoncore' project before cross-compiling
362362extensions is possible.
363363
364364Note that by default, Visual Studio 2008 does not install 64bit compilers or
0 commit comments