X-Git-Url: https://git.openafs.org/?p=openafs.git;a=blobdiff_plain;f=README-NT;h=4f973f0a9073552423a5b7c5b9758a4c3011636e;hp=40e4103fb6c41e79ecb608d7601ea68f330483f4;hb=09e871e52fac858a22b0b41a5f414b8b69a79e2d;hpb=66cf365c50efa09b0629cf3c211659b070457f63 diff --git a/README-NT b/README-NT index 40e4103..4f973f0 100644 --- a/README-NT +++ b/README-NT @@ -3,15 +3,25 @@ License. For details, see the LICENSE file in the top-level source directory or on-line at http://www.openafs.org/dl/license10.html The document now provides a step by step procedure that takes the user -from a basic Windows 2000/XP workstation to an OpenAFS development +from a basic Windows 2000/XP/2003 workstation to an OpenAFS development environment. Details are provided so that a 'beginning' windows developer can build an OpenAFS installable package for Windows 2000/XP/2003. -NOTE: +NOTE 1: As of the OpenAFS 1.3 release series, Windows platforms released prior to Windows 2000 are not being supported. The InstallShield installer is still in the source tree but is no longer supported. -A new open source installer based on NSIS 2.0 replaces it. +A new open source installer based on NSIS 2.07 replaces it. + +NOTE 2: +In this release, in addition to the production quality CIFS-AFS +gateway based client service there also exists an experimental +implementation of an Installable File System (IFS). +To build the IFS version, follow the directions below, but note that +only the NSIS installer script has been updated to support it. +Also, the IFS kernel module must be built separately, using the IFS/DDK +build environment. + *********** Windows 2000/XP/2003 Build Process **************** @@ -31,7 +41,7 @@ The following steps describe how to configure Windows 2000/XP: D. Configure NTBUILD.BAT E. Set program version Level F. Build Win2000 binaries - G. Install NSIS 2.0 + G. Install NSIS 2.07 H. Build NSIS Install Package I. Install Wix 2.0 J. Build Wix MSI Install Package @@ -42,14 +52,14 @@ The Microsoft development tools require anywhere from 660 MB to 1.8GB of storage depending on which compilers are selected. The following versions are supported: - Microsoft Visual .NET + Microsoft Visual Studio .NET available via a MSDN subscription - Microsoft Visual .NET 2003 (recommended) + Microsoft Visual Studio .NET 2003 (recommended) available via a MSDN subscription - Microsoft Visual C++ Toolkit 2003 (same as .NET 2003) - http://msdn.microsoft.com/visualc/vctoolkit2003/ + Microsoft Visual Studio .NET 2005 (do not use for production) + available via a MSDN subscription The following Microsoft SDK is required: @@ -59,14 +69,14 @@ The following Microsoft SDK is required: The following Microsoft DDK is required: - Microsoft Windows Server 2003 DDK + Microsoft Windows Server 2003 SP1 DDK available via a MSDN subscription or via free CD http://www.microsoft.com/whdc/devtools/ddk/orderddkcd.mspx The NSIS installer requires about 14 MB of storage. The following version is supported: - Nullsoft Scriptable Installation System 2.0 + Nullsoft Scriptable Installation System 2.07 http://nsis.sourceforge.net/home/ The WiX installer requires about 18 MB of storage. The following @@ -129,8 +139,8 @@ The AFS base directory should look something like the following: STEP B. Install compiler and development tools. -Install a copy of Microsoft Visual .NET, Visual .NET 2003, Visual C++ -Toolkit 2003. The "Typical" install setting is sufficient. +Install a copy of Microsoft Visual Studio .NET, Visual Studio .NET 2003, +or Visual Studio .NET 2005. The "Typical" install setting is sufficient. (1) You can reduce the installation size by selecting "Custom" install and remove all but the following Options: @@ -168,6 +178,11 @@ These files come from the following Microsoft DDKs/SDKs: netcfgn.h, netcfgx.h: Windows XP/2003 DDK - inc/wxp/ +If you are interested in experimenting with the IFS you must purchase from +Microsoft a copy of the Windows 2003 SP1 IFS Kit. + + http://www.microsoft.com/whdc/devtools/ifskit/default.mspx + STEP D. Configure NTBUILD.BAT. @@ -176,9 +191,9 @@ customized for use on your development system. The following variables must be defined to match your configuration: AFSVER_CL: Set to 1200 if using MS Visual C++ 6.0 - Set to 1300 if using MS Visual .NET - Set to 1310 if using MS Visual .NET 2003 - Set to 1400 if using MS Visual .NET 2005 + Set to 1300 if using MS Visual Studio .NET + Set to 1310 if using MS Visual Studio .NET 2003 + Set to 1400 if using MS Visual Studio .NET 2005 MSVCDIR: Set to the short name version of the directory into which the visual C++ compiler was installed regardless of version @@ -188,7 +203,8 @@ must be defined to match your configuration: NTDDKDIR: Set the short name of the directory containing the npapi.h file - AFSROOT: Set to the short name of the OpenAFS Base directory + AFSROOT: Set to the short name of the OpenAFS Base directory. This + cannot be set to a UNC path. STEP E. Set version and installation options (optional) @@ -199,7 +215,7 @@ from: http://grand.central.org/dl/cellservdb/CellServDB then copy it to %AFSROOT%\src\WINNT\install\NSIS and name it afsdcell.ini -Edit file %AFSROOT%\src\config\NTMakefile.i386_nt40 +Edit file %AFSROOT%\src\config\NTMakefile.i386_w2k AFSPRODUCT_VER_MAJOR - Version Major Number AFSPRODUCT_VER_MINOR - Version Minor Number AFSPRODUCT_VER_PATCH - Version Patch Number @@ -232,7 +248,7 @@ STEP F. Begin the build (3) Configure the environment variables: - For a release build: + For a release build (SMB version): (a) Execute the VCVARS32.BAT or VSVARS32.BAT file which part of the Visual Studio environment you installed. @@ -241,7 +257,16 @@ STEP F. Begin the build (c) Execute the NTBUILD.BAT file with the parameter "free" - For a debug build: + For a release build (IFS version): + + (a) Execute the VCVARS32.BAT or VSVARS32.BAT file which part of the + Visual Studio environment you installed. + + (b) Execute the SETENV.BAT file with the parameters "/2000 /RETAIL" + + (c) Execute the NTBUILD.BAT file with the parameter "free ifs" + + For a debug build (SMB version): (a) Execute the VCVARS32.BAT or VSVARS32.BAT file which part of the Visual Studio environment you installed. @@ -250,11 +275,20 @@ STEP F. Begin the build (c) Execute the NTBUILD.BAT file with the parameter "checked" + For a debug build (IFS version): + + (a) Execute the VCVARS32.BAT or VSVARS32.BAT file which part of the + Visual Studio environment you installed. + + (b) Execute the SETENV.BAT file with the parameters "/2000 /DEBUG" + + (c) Execute the NTBUILD.BAT file with the parameter "checked ifs" + (4) Clean the work area: nmake /f NTMakefile clean -(5) Build the complete Windows NT/2000 development environment. +(5) Build the complete Windows 2000/XP/2003 development environment. nmake /f NTMakefile install @@ -263,10 +297,13 @@ behavior is normal; the build process is successful as long as the build process doesn't terminate with an error ("nmake.exe return code 0x2") and it displays 'Build Finished Successfully'. +(6) [IFS only] Open a DDK/IFS Build Environment command window, change + to the src\WINNT\afsrdr directory, and execute the "build" command. + -STEP G. Install NSIS 2.0 (optional). +STEP G. Install NSIS 2.07 (optional). -Download the Nullsoft Scriptable Installation System (NSIS) 2.0 from +Download the Nullsoft Scriptable Installation System (NSIS) 2.07 from http://nsis.sourceforge.net/home/