[Zope-CVS] CVS: Packages/WinBuilders - README.txt:1.8

Tue Apr 12 23:30:56 EDT 2005

Update of /cvs-repository/Packages/WinBuilders
In directory cvs.zope.org:/tmp/cvs-serv24787

Modified Files:
	README.txt 
Log Message:

- Use a newer pywin32 build
- Update build instructions
- Use python 2.3.5 for the installer
- Service improvements


=== Packages/WinBuilders/README.txt 1.7 => 1.8 ===

--- Packages/WinBuilders/README.txt:1.7	Fri Jul 30 10:30:33 2004
+++ Packages/WinBuilders/README.txt	Tue Apr 12 23:30:26 2005
@@ -4,68 +4,70 @@
 without incident on XP.  It "almost works" on Win98SE (see bottom of
 file for discussion).
 
+Setup Environment
+------------------
+
 Install Cygwin from cygwin.org (the default installation should give
 you everything you need).
 
-Install Microsoft Visual C++ 6.0.
-
-Install InnoSetup 4.0 from www.jrsofware.org (into its default location).
-4.0.4-beta seems to work, while 4.0.7 does not.  Symptom: type error
-on compilation.  4.0.11 appears to work.
-
-Unpack this package into a directory.
-
-Launch a Cygwin bash shell.  If necessary, run the VCVARS.bat to set up
-the VC++ environment.  This shouldn't be necessary on Win2K, provided
-you've brought up the GUI at least once (MSDev doesn't finish writing
-all the registry keys it should until the GUI is first launched).  See
-below for Win98SE.
-
-If you're building Zope against Python 2.3.X, you may need to add some
-registry entries due to a bug in the distutils msvccompiler.py:
+Install Microsoft Visual C++ 6.0 (or MSVC 7 once we get to Python 2.4)
 
-[HKEY_CURRENT_USER\Software\Microsoft\DevStudio\6.0\Build System\Components\Platforms\Win32 (x86)\Directories]
-"path dirs"="c:\\windows\\system32;c:\\Program Files\\Microsoft Visual Studio\\Common\\Tools\\WinNT; c:\\Program Files\\Microsoft Visual Studio\\Common\\MSDev98\\Bin;c:\\Program Files\\Microsoft Visual Studio\\Common\\Tools;c:\\Program Files\\Microsoft Visual Studio\\VC98\\bin"
-"library dirs"="C:\\Program Files\\Microsoft Visual Studio\\VC98\\mfc\\lib;C:\\Program Files\\Microsoft Visual Studio\\VC98\\lib"
-"include dirs"="C:\\Program Files\\Microsoft Visual Studio\\VC98\\atl\\include;C:\\Program Files\\Microsoft Visual Studio\\VC98\\mfc\\include;C:\\Program Files\\Microsoft Visual Studio\\VC98\\include"
-
-This is unecessary if building against Python 2.2.X.  [Tim didn't find
-this necessary building against Python 2.3.3 and Christian against 2.3.4 either.]
-
-From the parent directory of the package, make a "tmp" directory.
-
-Get necessary source packages and place them in the tmp directory.  At the time
-of this writing, this includes:
-
-  - Python-2.3.4.tgz
-  - Python-2.3.4.exe (used for binary modules)
-  - win32all-163.exe
+Install InnoSetup 4.2 from www.jrsofware.org (into its default location).
+Versions earlier than 4.0.11 are known to not work; any 4.2.x release
+or later should be fine.
+
+From the parent directory of the package, make a "tmp" directory.  Place
+the necessary pre-requisites in this directory.  At the time of this writing, 
+this includes:
+
+  - Python-2.3.5.tgz
+  - Python-2.3.5.exe (used for binary modules)
+  - pywin32-204.win32-py2.3.exe (extracts binaries and sources)
   - Zope.tgz
 
-As time marches on, these version numbers will obviously change.
-
-If you see any make errors with references to one of these files, it's because
-you've not downloaded them or you've not placed them in 'tmp'.
+As time marches on, these version numbers will obviously change.  See 
+mk/python.mk for the exact versions required.
 
-From the parent directory of the package, type WinBuilders/buildout <type>
-where type is one of "python", "zope", or "zeo".
-
-For python, the buildout populates the "build" directory with a Python
-laid out for Zope and/or ZEO.
-
-For 'zope', the buildout populates the "build" directory with a Windows
-executable installer (read the Makfile.zope for special instructions).
-
-For 'zeo', the buildout populates the "build" directory with a Windows
-executable installer (read the Makefile.zeo for special instructions).
-
-
-
-Win98SE notes
--------------
-- You have to run vcvars32.bat to set up envars for MSVC 6.  Running that
-  from a bash shell doesn't have any effect on the Cygwin PATH.
-  This works:
+Building
+--------
+Launch a Cygwin bash shell, and from the parent directory, type:
+  WinBuilders/buildout <type>
+where type is one of "python", "zope", or "zeo".  Alternatively, you can 
+avoid the bash shell completely, and from a Windows command prompt type:
+  bash WinBuilders/buildout <type>
+
+Everything should work!
+  * For python, the buildout populates the "build" directory with a Python
+    laid out for Zope and/or ZEO.
+
+  * For 'zope', the buildout populates the "build" directory with a Windows
+    executable installer (read the Makefile.zope for special instructions).
+
+  * For 'zeo', the buildout populates the "build" directory with a Windows
+   executable installer (read the Makefile.zeo for special instructions).
+
+If the build fails:
+
+If the Windows drive you are working on is not C: (or Inno isn't installed 
+there!), try executing the following:
+  WinBuilders/buildout CYGROOT=/cygdrive/{your_drive_letter}
+
+If you see errors relating to MSVC not being installed, or the build process
+failing to find MSVC, it may be necessary to bring up the MSVC gui
+at least once (MSDev doesn't finish writing
+all the registry keys it should until the GUI is first launched).  If may
+also be necessary to run VCVARS.bat to set up the VC++ environment (but
+generally is not.)  See below for Win98SE.
+
+If you see any make errors with references to any of the files required
+in tmp/ (see 'Setup Environment' above), it's because a later version is
+now required, or the files you've downloaded are not in 'tmp'.
+
+All platform notes
+------------------
+- Depending on your MSVC installation options, you have to run vcvars32.bat 
+  to set up envars for MSVC.  Running that from a bash shell doesn't have any
+  effect on the Cygwin PATH. This works:
 
 + Open a native DOS box.
 + Run vcvars32.bat.
@@ -74,6 +76,8 @@
   desktop shortcut resolves to, so you can get the exact path by looking
   at the icon's Properties).
 
+Win98SE notes
+-------------
 - Every time a makefile runs xcopy, there's a segfault in kernel32.dll,
   which hangs the bash shell with an endless succession of error boxes.
   The only way I found to break out of this was to bring up the debugger,

