Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(30)

Unified Diff: PCbuild/readme.txt

Issue 15550: Trailing white spaces
Patch Set: Created 7 years, 6 months ago
Use n/p to move between diff chunks; N/P to move between comments. Please Sign in to add in-line comments.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « PCbuild/pyproject.props ('k') | PC/example_nt/readme.txt » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
--- a/PCbuild/readme.txt Sat Aug 04 16:17:10 2012 +0200
+++ b/PCbuild/readme.txt Sat Aug 04 22:46:03 2012 +0300
@@ -1,7 +1,7 @@
Building Python using VC++ 10.0
------------------------------
-This directory is used to build Python for Win32 and x64 platforms, e.g.
+This directory is used to build Python for Win32 and x64 platforms, e.g.
Windows 2000, XP, Vista and Windows Server 2008. In order to build 32-bit
debug and release executables, Microsoft Visual C++ 2008 Express Edition is
required at the very least. In order to build 64-bit debug and release
@@ -27,7 +27,7 @@
The solution is configured to build the projects in the correct order. "Build
Solution" or F7 takes care of dependencies except for x64 builds. To make
-cross compiling x64 builds on a 32bit OS possible the x64 builds require a
+cross compiling x64 builds on a 32bit OS possible the x64 builds require a
32bit version of Python.
NOTE:
@@ -47,7 +47,7 @@
Legacy support
--------------
-You can find build directories for older versions of Visual Studio and
+You can find build directories for older versions of Visual Studio and
Visual C++ in the PC directory. The legacy build directories are no longer
actively maintained and may not work out of the box.
@@ -108,7 +108,7 @@
within our pcbuild.sln, which means this module expects to find a
pre-built Tcl/Tk in either ..\..\tcltk for 32-bit or ..\..\tcltk64 for
64-bit (relative to this directory). See below for instructions to build
- Tcl/Tk.
+ Tcl/Tk.
_bz2
Python wrapper for the libbzip2 compression library. Homepage
http://www.bzip.org/
@@ -128,7 +128,7 @@
bzip2-1.0.6\ when you do a clean, so if you want to rebuild bzip2.lib
you need to clean up bzip2-1.0.6\ by hand.
- All of this managed to build libbz2.lib in
+ All of this managed to build libbz2.lib in
bzip2-1.0.6\$platform-$configuration\, which the Python project links in.
_lzma
Python wrapper for the liblzma compression library.
@@ -155,17 +155,17 @@
You must install the NASM assembler from
http://nasm.sf.net
for x86 builds. Put nasmw.exe anywhere in your PATH.
- Note: recent releases of nasm only have nasm.exe. Just rename it to
+ Note: recent releases of nasm only have nasm.exe. Just rename it to
nasmw.exe.
You can also install ActivePerl from
http://www.activestate.com/activeperl/
- if you like to use the official sources instead of the files from
+ if you like to use the official sources instead of the files from
python's subversion repository. The svn version contains pre-build
makefiles and assembly files.
The build process makes sure that no patented algorithms are included.
- For now RC5, MDC2 and IDEA are excluded from the build. You may have
+ For now RC5, MDC2 and IDEA are excluded from the build. You may have
to manually remove $(OBJ_D)\i_*.obj from ms\nt.mak if the build process
complains about missing files or forbidden IDEA. Again the files provided
in the subversion repository are already fixed.
@@ -186,16 +186,16 @@
this by hand.
The subprojects above wrap external projects Python doesn't control, and as
-such, a little more work is required in order to download the relevant source
+such, a little more work is required in order to download the relevant source
files for each project before they can be built. The buildbots do this each
-time they're built, so the easiest approach is to run either external.bat or
+time they're built, so the easiest approach is to run either external.bat or
external-amd64.bat in the ..\Tools\buildbot directory from ..\, i.e.:
C:\..\svn.python.org\projects\python\trunk\PCbuild>cd ..
C:\..\svn.python.org\projects\python\trunk>Tools\buildbot\external.bat
This extracts all the external subprojects from http://svn.python.org/external
-via Subversion (so you'll need an svn.exe on your PATH) and places them in
+via Subversion (so you'll need an svn.exe on your PATH) and places them in
..\.. (relative to this directory). The external(-amd64).bat scripts will
also build a debug build of Tcl/Tk; there aren't any equivalent batch files
for building release versions of Tcl/Tk lying around in the Tools\buildbot
@@ -238,7 +238,7 @@
junction as follows (using the directory structure above as an example):
C:\..\python\trunk\external <- already exists and has built versions
- of the external subprojects
+ of the external subprojects
C:\..\python\branches\py3k>linkd.exe external ..\..\trunk\external
Link created at: external
@@ -297,16 +297,16 @@
--------------
The solution has no configuration for static libraries. However it is easy
-it build a static library instead of a DLL. You simply have to set the
+it build a static library instead of a DLL. You simply have to set the
"Configuration Type" to "Static Library (.lib)" and alter the preprocessor
macro "Py_ENABLE_SHARED" to "Py_NO_ENABLE_SHARED". You may also have to
-change the "Runtime Library" from "Multi-threaded DLL (/MD)" to
+change the "Runtime Library" from "Multi-threaded DLL (/MD)" to
"Multi-threaded (/MT)".
Visual Studio properties
------------------------
-The PCbuild solution makes heavy use of Visual Studio property files
+The PCbuild solution makes heavy use of Visual Studio property files
(*.vsprops). The properties can be viewed and altered in the Property
Manager (View -> Other Windows -> Property Manager).
« no previous file with comments | « PCbuild/pyproject.props ('k') | PC/example_nt/readme.txt » ('j') | no next file with comments »

RSS Feeds Recent Issues | This issue
This is Rietveld 894c83f36cb7+