pcs 98/07/19 08:18:15
Modified: . how-to-release-win32.html
Log:
Update slightly to make the install directory/build directory
issue clearer. Also assume that the source files are coming from a
Unix distribution, since that is the most likely (and important) case.
Note the renaming of README.NT to README-NT.TXT.
Revision Changes Path
1.8 +46 -34 apache-devsite/how-to-release-win32.html
Index: how-to-release-win32.html
===================================================================
RCS file: /export/home/cvs/apache-devsite/how-to-release-win32.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- how-to-release-win32.html 1998/07/13 15:09:35 1.7
+++ how-to-release-win32.html 1998/07/19 15:18:14 1.8
@@ -49,16 +49,32 @@
<H2>Detailed Instructions</H2>
-Before starting this build, make sure that you have the correct
-version of Apache checked out, and that all the non-binary files have
-DOS style line endings. You will need a copy of the comercial product
-InstallShield Express 2.0. You will need that product and not
-InstallFromTheWeb, InstallShield 5, the ancient InstallShield 2, or
-any of the variants of InstallShield occasionally bundled with the Java
-or C development environments.
+Before starting this build, make sure that you have the correct Apache
+file tree available. This will normally by a normal Unix release
+archive. Make sure that all the non-binary files have DOS style line
+endings. You will need a copy of the comercial product InstallShield
+Express 2.0. You will need that product and not InstallFromTheWeb,
+InstallShield 5, the ancient InstallShield 2, or any of the variants
+of InstallShield occasionally bundled with the Java or C development
+environments.
<P>
+Building the Windows installer requires to temporary directories.
+
+<UL>
+
+<LI>An <i>install directory</i> which contains the files that
+ IS2 will use to build the installer. This document uses
+ <SAMP>C:\Apache</SAMP> for the install directory.
+
+<LI>A <i>build directory</i> where Apache will be built. Once built the
+ binary files will be installed into the install directory so that
+ IS2 can find them. This document uses <SAMP>C:\Build</SAMP> for
+ the build directory.
+
+</UL>
+
<OL>
<LI><STRONG>Create The Install Directory</STRONG><P>
@@ -73,24 +89,29 @@
<P>
-Now create the install directory, and extract Apache into it. The
-Apache files will normally come either direct from CVS at a given tag
-value, or from an existing Unix source distribution. If the
-distribution has Unix line endings, convert the line endings of all
-files apart from <SAMP>htdocs/*.gif</SAMP> and
+Now create the install directory, and extract the Apache Unix release
+archive into it. If the distribution has Unix line endings, convert
+the line endings of all files apart from <SAMP>htdocs/*.gif</SAMP> and
<SAMP>icons/*.gif</SAMP>.
<P>
+
+Copy the whole of the install directory to the build directory.
+
+<P>
-The following directories are not needed on Windows because they
-are not part of the installer:
+The following directories are not needed in the install directory on
+Windows because they are not part of the installer:
+
+<P>
<UL>
- <LI><SAMP>conf\*.conf-dist</SAMP> (but leave the
<SAMP>*.conf-dist-win</SAMP>)
+ <LI><SAMP>conf\*.conf-dist</SAMP> (but leave the
+ <SAMP>*.conf-dist-win</SAMP> files)
<LI><SAMP>src\os\{emx,bs2000,unix}</SAMP>
<LI><SAMP>src\helpers</SAMP>
- <LI><SAMP>src\test</SAMP>
- <LI><SAMP>src\modules\test</SAMP>
+ <LI><SAMP>src\test</SAMP> (not normally part of the Unix release)
+ <LI><SAMP>src\modules\test</SAMP> (not normally part of the Unix release)
</UL>
<P>
@@ -102,11 +123,8 @@
<P>
-You will also need to build the executables and DLLs. This should
-<STRONG>not</STRONG> be done in the same directory where you are
-building the installer. Instead, copy your install directory to a
-temporary directory name (this can be any directory, but the examples
-below will assume that it is <SAMP>C:\BUILD</SAMP>).
+Rename the file <SAMP>README.NT</SAMP> in the install directory to
+<SAMP>README-NT.TXT</SAMP>.
<P>
@@ -124,7 +142,7 @@
<LI><STRONG>Configure the InstallShield Configuration File</STRONG><P>
-Apache for Windows is packaged using InstallShield Express 2. This use the
+Apache for Windows is packaged using InstallShield Express 2. This uses the
configuration file
<SAMP>os/win32/installer/apache.iwz</SAMP>. Unfortunately
InstallShield's configuration file contains hard-coded absolute paths
@@ -136,12 +154,6 @@
<P>
-<STRONG>Note</STRONG>: This is probably a good time to check that the version
-information in the <SAMP>apache.iwz</SAMP> file is up-to-date. The
-version is stored in these locations:
-
-<P>
-
Start InstallShield Express 2, then load the
<SAMP>os/win32/installer/apache.iwz</SAMP> file from the build
directory (e.g. <SAMP>\BUILD</SAMP>). Inside InstallShield, perform
@@ -160,7 +172,7 @@
add or remove any files added or removed since the last time the
configuration file was updated (NB: certain Unix only files
may not need to be added, if they are not needed by Windows
- end users).
+ end users).
</LI>
<LI>Set the Visual Design, Application Information, Version. This
should contain the full version number, eg. 1.3.0 or 1.3b5.
@@ -240,7 +252,7 @@
| MSVCRT.DLL
| README
| README.configure
- | README.NT
+ | README-NT.TXT
| STATUS
|
|--- conf
@@ -293,9 +305,9 @@
<P>
-At the end of the installation, the user will have the option of
-viewing a <SAMP>README</SAMP>. This will be the <SAMP>README.NT</SAMP>
-file.
+At the end of the installation, the user will have the option of viewing a
+<SAMP>README</SAMP>. This will be the <SAMP>README-NT.TXT</SAMP> file (which
+is the file <SAMP>README.NT</SAMP> in CVS).
<P>
