"Fossies" - the Fresh Open Source Software Archive
Member "bind-9.11.23/win32utils/legacy/win32-build.txt" (7 Sep 2020, 4140 Bytes) of package /linux/misc/dns/bind9/9.11.23/bind-9.11.23.tar.gz:
As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard
) with prefixed line numbers.
Alternatively you can here view
the uninterpreted source code file.
For more information about "win32-build.txt" see the Fossies "Dox" file reference
1 Copyright (C) Internet Systems Consortium, Inc. ("ISC")
3 See COPYRIGHT in the source root or http://isc.org/copyright.html for terms.
5 *LEGACY* BIND 9.10 for Win32 Source Build Instructions. 04-Feb-2014
7 Building BIND 9.10 on Windows using legacy compilers (up to Visual
8 Studio 2008) has the following prerequisites:
10 1) Perl, 2) Visual C++ redistributable object, 3) OpenSSL, and
11 optionally 4) LibXML2, 5) LibGeoIP, and 6) Readline.
12 See ..\build.txt for more details on these prerequisites.
14 If you want to build using Visual C++ 6.0, you'll need some extra
15 files that are to be found in the Platform SDK (which you will need
16 to install), namely:
23 You'll also need an updated Iprtrmib.h - using the VC++6.0 one will
24 get you some compilation errors. You can just overwrite the old one if
25 you're not using it for any purposes, and maybe keep a backup of it.
27 You can copy the header files under VC98\INCLUDE and the library file
28 under VC98\LIB. I think you can also put them in a separate directory
29 and add it to the include search list, but I don't know if that can be
30 made persistent.
32 For building on VC++ 7.0 or more recent, no extra files are required.
34 The instructions assume a Visual C++ 6.0 compiler with Visual Studio
35 and Visual Studio Service Pack 3 or later. It may build and work with
36 earlier versions but it has not been tested. The binaries may be built
37 and run on any of the following platforms: NT 4.0 Workstation (SP3 or
38 later), NT 4.0 Server (SP3 or later), Windows 2000 Professional (SP1
39 or later), Windows 2000 Server or any kind (SP1 or later), Windows XP,
40 Windows 2003 Server, Windows Vista, Windows 2008 Server, Windows 7,
41 Windows 2008 R2 Server, Windows 8, Windows 2012 Server (untested), and
42 further (untested as not yet available). It will NOT build or run on
43 Windows 95, Windows 98, etc., or Windows RT platforms.
45 BUILDING BIND
47 From the command prompt cd to the win32utils\legacy directory under
48 the BIND9 root:
50 cd bind-9.10.0\win32utils\legacy
52 If you wish to use nmake from VC++ 6.0 or more recent, run
53 the BuildAll.bat file:
57 This will do the following:
58 1) Build the gen application in the lib/dns directory.
59 2) Run the gen application and build the required lib/dns header
61 3) Create the Build/Release subdirectory under the root of the BIND
62 source tree which will hold the binaries being built.
63 4) Build the libraries, named, application tools like dig, rndc
64 dnssec tools, installer, checkconf and checkzones programs,
65 BIND 9 Installer.
66 5) Copies the release notes and the OpenSSL DLL to the BUILD/Release
68 6) Copies the BIND 9 ARM HTML files and the application HTML files
69 to the Build\Release area.
71 If you wish to use the Visual Studio GUI for building, you can just
72 run the BuildSetup.bat file:
76 This will create or find and copy into place several files which are
77 necessary for the build to proceed. It also locates and copies into place
78 the DLLs for OpenSSL and libxml2.
80 Use BINDBuild.dsw (also located in the win32utils\legacy directory) to
81 open the workspace for all of the BIND9 libraries and applications. If
82 needed Visual Studio will update the workspace (aka solution) and
83 project files. Note it is known to give slightly incorrect files on VS
84 2010 or more recent, for instance BINDInstall is not compiled to use
85 DLLs. Finally select "Build->Batch Build", click "Select All", then
86 click "Build".
88 After the build has completed, run the BuildPost.bat file:
92 ...which does post-build processing.
94 Installation is accomplished by running the BINDInstall program. All
95 DLL's are copied to the Program Files area and all applications
96 (including BINDInstall which may be necessary for uninstalling BIND 9)
97 to the bin directory. If BIND 8 has previously been installed on the
98 system it must be uninstalled first by running it's own BINDInstall
99 program. The BIND 9 installer does not yet do this.
101 All bugs found, whether in the process of building the application or
102 running BIND or the tools should be reported to the bind9 bugs email
103 account at email@example.com.