From bb9296e1a8db3ace122d8ec4ca57b2c7554c7040 Mon Sep 17 00:00:00 2001 From: Mark Andrews Date: Tue, 1 Nov 2005 05:49:15 +0000 Subject: [PATCH] update --- win32utils/win32-build.txt | 64 +++++++++++++++++++++++++++++--------- 1 file changed, 49 insertions(+), 15 deletions(-) diff --git a/win32utils/win32-build.txt b/win32utils/win32-build.txt index cb0b537e69..fdc1028337 100644 --- a/win32utils/win32-build.txt +++ b/win32utils/win32-build.txt @@ -2,33 +2,50 @@ Copyright (C) 2004, 2005 Internet Systems Consortium, Inc. ("ISC") Copyright (C) 2001, 2002 Internet Software Consortium. See COPYRIGHT in the source root or http://isc.org/copyright.html for terms. -$Id: win32-build.txt,v 1.10 2005/09/06 03:51:37 marka Exp $ +$Id: win32-build.txt,v 1.11 2005/11/01 05:49:15 marka Exp $ - BIND 9.4 for Win32 Source Build Instructions. 28-Jul-2001 + BIND 9.4 for Win32 Source Build Instructions. 28-May-2005 + +Building BIND 9.4 on Windows NT/2000 has the following prerequisites: -Building BIND 9.4 on Windows NT/2000 has two prerequisites: 1) You need to install Perl for Windows NT/2000. ActiveState (http://www.activestate.com/) is the one most people install and use; 2) OpenSSL (http://www.openssl.org) needs to be downloaded and built on the system on which you are building BIND. +3) If you want to build using Visual C++ 6.0, you'll need some extra +files that are to be found in the Platform SDK (which you will need +to install), namely: + +iphlpapi.h +iptypes.h +ipexport.h +iphlpapi.lib + +You'll also need an updated Iprtrmib.h - using the VC++6.0 one will +get you some compilation errors. You can just overwrite the old one if +you're not using it for any purposes, and maybe keep a backup of it. + +You can copy the header files under VC98\INCLUDE and the library file +under VC98\LIB. I think you can also put them in a separate directory +and add it to the include search list, but I don't know if that can be +made persistent. + +For building on VC++ 7.0 no extra files are required. The instructions assume a Visual C++ 6.0 compiler with Visual Studio and Visual Studio Service Pack 3 or later. It may build and work with earlier versions but it has not been tested. The binaries may be built and run on any of the following platforms: NT 4.0 Workstation (SP3 or later), NT 4.0 Server (SP3 or later), Windows 2000 Professional (SP1 or later), -Windows 2000 Server or any kind (SP1 or later). It should run on the -to-be-released Windows XP platforms of various flavors. It will NOT build -or run on Windows 95, Windows 98, etc. platforms. +Windows 2000 Server or any kind (SP1 or later), Windows XP, Windows 2003 +Server. It will NOT build or run on Windows 95, Windows 98, etc. platforms. Step 1: Download and Build OpenSSL Download and untar the OpenSSL sources from http://www.openssl.org/. if you have place the BIND sources in /BIND9 you should place the -OpenSSL sources in /OpenSSL-0.9.6g. If you place the sources anywhere -else you will have to edit the libdns.dsp or libdns.mak files to point -the include directories and the link library location to the correct -places as well as move the DLL to the BUILD/Release subdirectory. +OpenSSL sources in /openssl-0.9.7c or the appropriate directory name +created when you untarred the openssl tarball. Note: Building OpenSSL also requires that you install Perl as it uses it during its build process. Follow the instructions for NT given @@ -38,6 +55,8 @@ and libeay32.dll in the out32dll subdirectory. Step 2 Building BIND +You must build openssl first. + From the command prompt cd to the win32utils under the BIND root. Execute the BuildAll.bat file. This will do the following: 1) copy config.h.win32 to config.h in the root. @@ -63,6 +82,7 @@ directory as this file. The following files are built: +libbind9.dll libisc.dll libdns.dll libisccc.dll @@ -84,10 +104,24 @@ named-checkzone.exe dnssec-keygen.exe dnssec-signzone.exe -You should end up with 20 binaries in the bind9/Build/Release -directory. The Install instructions Readme1st.txt from win32utils -and libeay32.dll from the openssl/out32dll/ directory are also copied -into the Build area. In addition you should have 22 HTML files. +If you are building with VS.NET (aka VC++ V7) you will need additional +system DLL's: + +mfc71.dll +msvcr71.dll + +or + +mfc70.dll +msvcr70.dll + +depending on your version of the compiler. + +You should end up with 18-20 binaries in the bind9/Build/Release +directory. The Install instructions Readme1st.txt from win32utils and +libeay32.dll from the openssl/out32dll/ directory are also copied into +the Build area. In addition you should have 22 HTML files and a number +of text files. The set of files in the directory bind9/Build/Release form the installation kit which can then be zipped and distributed to any @@ -105,6 +139,6 @@ running BIND or the tools should be reported to the bind9 bugs email account at bind9-bugs@isc.org. Danny Mayer - danny.mayer@nominum.com + mayer@ntp.isc.org