[Python-checkins] r59624 - in python/trunk: Misc/NEWS PCbuild PCbuild/readme.txt PCbuild9

[christian.heimes]

Author: christian.heimes
Date: Mon Dec 31 16:18:55 2007
New Revision: 59624

Added:
   python/trunk/PCbuild/
      - copied from r59623, python/trunk/PCbuild9/
Removed:
   python/trunk/PCbuild9/
Modified:
   python/trunk/Misc/NEWS
   python/trunk/PCbuild/readme.txt
Log:
Renamed PCBuild9 directory to PCBuild

Modified: python/trunk/Misc/NEWS
==============================================================================
--- python/trunk/Misc/NEWS	(original)
+++ python/trunk/Misc/NEWS	Mon Dec 31 16:18:55 2007
@@ -12,6 +12,9 @@
 Core and builtins
 -----------------
 
+- Moved PCbuild/ directory for VS 2003 to PC/VS7.1 and renamed PCBuild9/
+  directory to PCBuild/.
+
 - Issue #1629: Renamed Py_Size, Py_Type and Py_Refcnt to Py_SIZE, Py_TYPE
   and Py_REFCNT.
 

Modified: python/trunk/PCbuild/readme.txt
==============================================================================
--- python/trunk/PCbuild9/readme.txt	(original)
+++ python/trunk/PCbuild/readme.txt	Mon Dec 31 16:18:55 2007
@@ -11,7 +11,7 @@
 you are going to create an optimized build you want to select "Release" as
 configuration.
 
-The PCbuild9 directory is compatible with all versions of Visual Studio from
+The PCbuild directory is compatible with all versions of Visual Studio from
 VS C++ Express Edition over the standard edition up to the professional
 edition. However the express edition does support features like solution
 folders or profile guided optimization (PGO). The missing bits and pieces
@@ -32,7 +32,7 @@
 When using the Debug setting, the output files have a _d added to
 their name:  python30_d.dll, python_d.exe, parser_d.pyd, and so on.
 
-The 32bit builds end up in the solution folder PCbuild9 while the x64 builds
+The 32bit builds end up in the solution folder PCbuild while the x64 builds
 land in the amd64 subfolder. The PGI and PGO builds for profile guided
 optimization end up in their own folders, too.
 
@@ -67,7 +67,7 @@
 The following subprojects will generally NOT build out of the box. They
 wrap code Python doesn't control, and you'll need to download the base
 packages first and unpack them into siblings of PCbuilds's parent
-directory; for example, if your PCbuild9 is  ..\dist\py3k\PCbuild9\,
+directory; for example, if your PCbuild is  ..\dist\py3k\PCbuild\,
 unpack into new subdirectories of ..\dist\.
 
 _tkinter
@@ -85,7 +85,7 @@
 
     Build with build_tkinter.py
     ---------------------------
-    The PCbuild9 directory contains a Python script which automates all
+    The PCbuild directory contains a Python script which automates all
     steps. Run the script in a Visual Studio 2009 command prompt with 
 
       python build_tkinter.py Win32
@@ -145,7 +145,7 @@
 
     A custom pre-link step in the bz2 project settings should manage to
     build bzip2-1.0.3\libbz2.lib by magic before bz2.pyd (or bz2_d.pyd) is
-    linked in PCbuild9\.
+    linked in PCbuild\.
     However, the bz2 project is not smart enough to remove anything under
     bzip2-1.0.3\ when you do a clean, so if you want to rebuild bzip2.lib
     you need to clean up bzip2-1.0.3\ by hand.
@@ -304,7 +304,7 @@
 Visual Studio properties
 ------------------------
 
-The PCbuild9 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).