Removed PCbuild8/ directory and added a new build directory for VS 2005

based on the VS 2008 build directory to PC/VS8.0. The script
PCbuild/vs8to9.py was added to sync changes from PCbuild to PC/VS8.0.

Kristjan, the initial creator of the PCbuild8 directory is fine with the replacement. I've moved the new version of the VS 2005 build directory next to the other legacy build directories. The new sync script is based on the work of wreck and syncs changes in the project, property and solution files.

1 files changed, 41 insertions, 0 deletions

diff --git a/PC/VS8.0/build_pgo.bat b/PC/VS8.0/build_pgo.bat
new file mode 100644
index 0000000..d28a767
--- /dev/null
+++ b/PC/VS8.0/build_pgo.bat
@@ -0,0 +1,41 @@
+@echo off

+rem A batch program to build PGO (Profile guided optimization) by first

+rem building instrumented binaries, then running the testsuite, and

+rem finally building the optimized code.

+rem Note, after the first instrumented run, one can just keep on

+rem building the PGUpdate configuration while developing.

+

+setlocal

+set platf=Win32

+

+rem use the performance testsuite.  This is quick and simple

+set job1=..\..\tools\pybench\pybench.py -n 1 -C 1 --with-gc

+set path1=..\..\tools\pybench

+

+rem or the whole testsuite for more thorough testing

+set job2=..\..\lib\test\regrtest.py

+set path2=..\..\lib

+

+set job=%job1%

+set clrpath=%path1%

+

+:CheckOpts

+if "%1"=="-p" (set platf=%2) & shift & shift & goto CheckOpts

+if "%1"=="-2" (set job=%job2%) & (set clrpath=%path2%) & shift & goto CheckOpts

+

+set PGI=%platf%-pgi

+set PGO=%platf%-pgo

+

+@echo on

+rem build the instrumented version

+call build -p %platf% -c PGInstrument

+

+rem remove .pyc files, .pgc files and execute the job

+%PGI%\python.exe rmpyc.py %clrpath%

+del %PGI%\*.pgc

+%PGI%\python.exe %job%

+

+rem finally build the optimized version

+if exist %PGO% del /s /q %PGO%

+call build -p %platf% -c PGUpdate

+