source: trunk/third/bind/win32utils/win32-build.txt @ 21744

Revision 21744, 4.4 KB checked in by ghudson, 20 years ago (diff)
This commit was generated by cvs2svn to compensate for changes in r21743, which included commits to RCS files with non-trunk default branches.
Line 
1Copyright (C) 2004  Internet Systems Consortium, Inc. ("ISC")
2Copyright (C) 2001, 2002  Internet Software Consortium.
3See COPYRIGHT in the source root or http://isc.org/copyright.html for terms.
4
5$Id: win32-build.txt,v 1.1.1.2 2005-04-15 15:30:49 ghudson Exp $
6
7       BIND 9.2.0 Beta for Win32 Source Build Instructions.  28-Jul-2001
8
9Building BIND 9.2 on Windows NT/2000 has two prerequisites:
101) You need to install Perl for Windows NT/2000. ActiveState
11(http://www.activestate.com/) is the one most people install and use;
122) OpenSSL (http://www.openssl.org) needs to be downloaded and built
13on the system on which you are building BIND.
14
15The instructions assume a Visual C++ 6.0 compiler with Visual Studio and
16Visual Studio Service Pack 3 or later. It may build and work with earlier
17versions but it has not been tested. The binaries may be built and run on
18any of the following platforms: NT 4.0 Workstation (SP3 or later), NT 4.0
19Server (SP3 or later), Windows 2000 Professional (SP1 or later),
20Windows 2000 Server or any kind (SP1 or later). It should run on the
21to-be-released Windows XP platforms of various flavors. It will NOT build
22or run on Windows 95, Windows 98, etc. platforms.
23
24Step 1: Download and Build OpenSSL
25
26Download and untar the OpenSSL sources from http://www.openssl.org/.
27if you have place the BIND sources in /BIND9 you should place the
28OpenSSL sources in /OpenSSL-0.9.6b. If you place the sources anywhere
29else you will have to edit the libdns.dsp or libdns.mak files to point
30the include directories and the link library location to the correct
31places as well as move the DLL to the BUILD/Release subdirectory.
32
33Note: Building OpenSSL also requires that you install Perl as it uses
34it during its build process. Follow the instructions for NT given
35in the INSTALL.W32 file to build the kit. This will produce libeay32.lib
36and libeay32.dll in the out32dll subdirectory.
37
38
39Step 2 Building BIND
40
41From the command prompt cd to the win32utils under the BIND root.
42Execute the BuildAll.bat file. This will do the following:
431) copy config.h.win32 to config.h in the root.
442) create the versions.h file in the root.
453) Build the gen application in the lib/dns directory.
464) Run the gen application and build the required lib/dns header
47   files.
485) Create the Build/Release subdirectory under the root of the BIND
49   source tree which will hold the binaries being built.
506) Build the libraries, named, application tools like dig, rndc
51   dnssec tools, installer, checkconf and checkzones programs,
52   BIND 9 Installer.
537) Copies the release notes and the OpenSSL DLL to the BUILD/Release
54   directory.
558) Copies the BIND 9 ARM HTML files and the application HTML files
56   to the Build\Release area.
57
58If you wish to use Visual Studio for building, you can just run the
59BuildSetup.bat file which will create all the necessary files and you
60can then use the BINDBuild.dsw to open the workspace for all of the
61libraries and applications. These files reside in the same win32utils
62directory as this file.
63
64The following files are built:
65
66libisc.dll
67libdns.dll
68libisccc.dll
69libisccfg.dll
70liblwres.dll
71named.exe
72bindevt.dll
73BINDInstall.exe
74
75rndc.exe
76dig.exe
77host.exe
78nslookup.exe
79nsupdate.exe
80
81named-checkconf.exe
82named-checkzone.exe
83
84dnssec-keygen.exe
85dnssec-makekeyset.exe
86dnssec-signkey.exe
87dnssec-signzone.exe
88
89You should end up with 20 binaries in the bind9/Build/Release
90directory. The Install instructions Readme1st.txt from win32utils
91and libeay32.dll from the openssl/out32dll/ directory are also copied
92into the Build area. In addition you should have 22 HTML files.
93
94The set of files in the directory bind9/Build/Release form the
95installation kit which can then be zipped and distributed to any
96suitable Windows NT 4.0 or Windows 2000 platform.
97
98Installation is accomplished by running the BINDInstall program. All DLL's
99are copied to the system32 area and all applications (including BINDInstall
100which may be necessary for uninstalling BIND 9) to the dns/bin directory.
101If BIND 8 has previously been installed on the system it must be uninstalled
102first by running it's own BINDInstall program.  The BIND 9 installer does
103not yet do this.
104
105All bugs found, whether in the process of building the application or
106running BIND or the tools should be reported to the bind9 bugs email
107account at bind9-bugs@isc.org.
108
109        Danny Mayer
110        danny.mayer@nominum.com
111
112
Note: See TracBrowser for help on using the repository browser.