1 Compiling RRDtool 1.1.x on Win32 with Microsoft Visual C++:
2 ---------------------------------------------------------------
4 to help windows deal with the reentrant versions of many unix
5 calls link with win32comp.c
8 The windows implementation of strftime does not seem to support
9 the ISO 8601 week number (%V) I have therfore included the file
10 strftime.[ch] which provides strftime_ ... if you compile rrdtool
11 with -Dstrftime=_strftime and link strftime.o then you will
12 get propper support for %V.
16 As of Jan 2004, code for libraries utilized by rrdtool
17 (png, libart, freetype, and zlib) is no longer distributed with
18 rrdtool. This requires some changes to the compile process on
19 Win32. The solution described here is to compile rrdtool to
20 link against these libraries dynamically. There is an advantage
21 to this approach: namely the rrdtool distribution doesn't have to
22 worry about how to compile these libraries on Win32. In theory,
23 since others already provide and maintain Win32 binaries for these
24 libraries the users don't have to worry about how to compile them
25 either. The disadvantage of this approach is that the DLLs for
26 these libraries must be available on the hosts where rrdtool will run.
28 Here are step by step instructions for compiling rrdtool.exe and
29 the perl shared library (RRDS.dll) with Microsoft Visual C++ 6.0.
30 (1) Download libraries rrdtool depends on from GnuWin32:
31 http://gnuwin32.sourceforge.net/
32 For freetype, libpng, and zlib download the "Complete Package"; each of
33 these will be a self-extracting self-installing executable.
34 For libart, download both the "Binaries" and "Developer Files" packages.
35 Unfortunately at this time GnuWin32 doesn't provide the "Complete Package"
36 installer for libart. Perhaps by the time you are following these
37 instructions GnuWin32 will have a "Complete Package" for libart.
38 (2) Install the GnuWin32 libraries by running the executables for freetype,
39 libpng, and zlib. These instructions and the Visual C++ project files
40 distributed with rrdtool assume that you will use the default install
41 location: C:\Program Files\GnuWin32. Extract the two zip files for libart,
42 libart-2.3.3-bin.zip and libart-2.3.3-1-lib.zip into the GnuWin32 directory;
43 the appropriate libart files will be added to the include, lib, and bin
45 (3) Add C:\Program Files\GnuWin32\bin to the PATH (Control Panel ->
46 System -> Advanced -> Environment Variables).
47 (4) Start Microsoft Visual C++ 6.0. Load the workspace file, rrdtool.dsw,
48 from the src subdirectory of your rrdtool code directory.
49 (5) Compile the Release build of the rrdtool project (since rrdtool depends
50 on the rrd project, the rrd library will also be compiled). At this
51 time, the compile will fail in zconf.h, a zlib header file. The problem
52 is a preprocessor directive that loads unistd.h. Open zconf.h in VC++
53 (this file is in C:\Program Files\GnuWin32\include) and find the following
56 #if 1 /* HAVE_UNISTD_H -- this line is updated by ./configure */
57 # include <sys/types.h> /* for off_t */
58 # include <unistd.h> /* for SEEK_* and off_t */
60 # include <unixio.h> /* for off_t */
62 # define z_off_t off_t
65 Change it to reads as follows (this is code from zlib-1.1.4):
68 # include <sys/types.h> /* for off_t */
69 # include <unistd.h> /* for SEEK_* and off_t */
71 # include <unixio.h> /* for off_t */
73 # define z_off_t off_t
76 Note that it is actually just a one line change. Save the file and
77 recompile rrdtool. By the time you are following these instructions
78 this issue with zconf.h may be resolved.
79 (6) At this point, you can run the executable rrdtool.exe in the
80 src\toolrelease subdirectory. Note that if you wish to run rrdtool
81 on other machines, you will need the following DLLs installed (on the
82 path) on those machines:
88 The names of the first four DLLs might vary from what is listed here
89 depending on the versions of the packages you downloaded from GnuWin32.
90 The fifth DLL, msvcrt.dll, is a system DLL for most versions of Windows.
91 If you are running on old version of Windows, you can install/upgrade to
92 IE4.0 to get this DLL.
93 (7) To compile the perl-shared library, open a Command Prompt (DOS box)
94 and cd to the bindings\perl-shared subdirectory.
95 (8) Run vcvars32.bat; this batch file, in your vc98\bin directory will
96 set necessary environment options for command line compiling.
97 (9) In bindings\perl-shared, run
101 If nmake test succeeds, you are good to go. RRDs.dll is in
102 blib\arch\auto\RRDs. If you plan to install via the Active State ppm
103 tool, tar and gzip the blib directory. You can use the RRDs.ppd file
104 in bindings\perl-shared directory. Remember that as in the case of
105 rrdtool.exe you will need the DLLs listed in (6) on the machine where
106 you are going to use RRDs.dll.
108 Microsoft Visual C++ 7.1 (.NET 2003):
110 Unfortunately, this is more difficult than with VC++ 6.0. The problem
111 is that by default the C runtime dll for VC++ 7.1 is msvcr71.dll rather
112 than msvcrt.dll. The GnuWin32 library binaries are all compiled
113 to use msvcrt.dll and you can't mix msvcr71.dll and msvcrt.dll in the
114 same process. One option is to download the source code for the libraries
115 (available from http://gnuwin32.sourceforge.net) recompile them with
116 VC++ 7.l. Then all the components will use msvcr71.dll. Once you are
117 going to go this route, you can also use static multi-threaded libraries
118 and use static linking between rrdtool (or RRDs.dll) and its dependencies.
120 To use the GnuWin32 library binaries, you need to trick VC++ 7.1 into
121 compiling rrdtool to use the older msvcrt.dll. Follow steps (1) - (3)
123 (4) Obtain a different version of the msvcrt.lib import library that
124 is compatible with vc7 and points to msvcrt.dll:
125 msvcrtlib_for_vc7.zip from http://xchat.org/win32/testing
126 Backup msvcrt.lib in your vc7\lib directory
127 (\Program Files\Microsoft Visual Studio .NET 2003\vc7\lib)
128 Then extract the msvcrt.lib from the zip file into the vc7\lib directory.
129 WARNING: Use this msvcrt.lib at your own risk! This is not a Microsoft
130 supplied file nor a file supported by anyone associated with rrdtool.
131 (5) Start Microsoft Visual C++ 7.1. Load the solution file, rrdtool.sln,
132 from the src subdirectory of your rrdtool code directory. Edit zconf.h,
133 as needed, as described under (5) above. Compile the release build of
135 Proceed with steps (6) - (9) as above, if you are using/picking up
136 the wrong msvcrt.lib import library then nmake test for perl-shared
139 Note: it is possible in the future that GnuWin32 will provide Win32
140 binaries that utilize msvcr71.dll rather than msvcrt.dll.
144 These notes share some insight I gained compiling 1.1.x with
145 MS Visual C++ 6.0 (using project files). This information may or
146 may not be accurate at the time you are reading this.
148 (1) freetype and rrdtool cannot use precompiled headers (which are
149 enabled by default for MSVC++ projects). MSVC++ 6.0 does not
150 support precompiled headers if #include directives contain MACROS.
151 (2) Compile Release build with Default optimization, not the
152 Maximize Speed optimization. I encountered some strange errors
153 (related to argument processing for complex commands like graph--
154 perhaps the getopt stuff is too blame) with Maximize Speed.
155 (3) libart relies upon config.h (ostensibly generated by the
156 configure script-- but of course not on Win32 platforms). ..\..\confignt
157 (which contains a static Win32 version of config.h) should be on
159 (4) Fonts are located in the %windir%\fonts, so the default font
160 is c:\winnt\fonts\cour.ttf. (6/19/02) At Kerry Calvert's suggestion
161 this setting was moved to confignt\config.h.
162 (5) libart requires a custom build step to generate art_config.h; this
163 is done manually via the commands:
164 cl -I..\..\confignt gen_art_config.c
165 gen_art_config.exe > art_config.h
167 Currently, to compile rrd.lib and rrdtool.exe using
168 the MSVC++ project files, first start MSVC++ 6.0. Open the rrdtool
169 workspace (rrdtool.dsw in the src directory). The active project/
170 configuration should be rrdtool-Win32 Release. Select Rebuild All
171 from the Build menu. The static link library (rrd.lib) will
172 be generated in src\release directory and executable will be generated
173 in the src\toolrelease directory.
175 Compiling RRDtool on NT ... work in progress
176 ---------------------------------------------------------------
177 by Tamas Kovacshazy (khazy@mit.bme.hu)
179 Persisting Problems with the current NT port:
181 Unfortunately, the RRD perl modules does not work with Perl
182 (ActivePerl) using the current distribution.
184 The RRD shared perl module can be compiled after some
189 0. Install perl if you do not have it!
190 Visit http://www.ActiveState.com/pw32/ for a complete distribution.
192 1. Copy ..\gd1.2\release\gd.lib to ..\gd1.2\
193 2. Copy ..\src\release\rrd.lib to ..\src
196 In this step the system complains about something I do not
197 understand. The error message is the following:
199 Note (probably harmless): No library found for '-lm'
201 Is a library missing? But it does not stop with an error...
203 4. nmake test (You must have Visual C++ on the machine!)
205 After these steps it generates the test files (svgs and rrds),
206 and they seem to be good.
208 The real problem in the shared perl modul is the following:
210 I do not know how this installation stuff works. The problem is
211 that the installation stuff looks for the gd.lib and the
212 rrd.lib in the ..\gd1.2 and ..\src directory. The UNIX compile
213 puts the files into these directories, but the NT compile does
220 Tamas Kovacshazy E-mail: khazy@mit.bme.hu
221 WWW: http://www.mit.bme.hu/~khazy
222 Technical University of Budapest
223 Department of Measurement and Information Systems