X-Git-Url: https://git.octo.it/?p=rrdtool.git;a=blobdiff_plain;f=NT-BUILD-TIPS.txt;h=d163d3f195a81acc0e44e606f75bac15ed02d606;hp=882ee953769366cc589717f08afa7a4aebecb6df;hb=0fe03275068c0e55d01a7cc2308fa12fdee569cf;hpb=5837606887a6d81e8b1f7588525cb1c8783fb62b

diff --git a/NT-BUILD-TIPS.txt b/NT-BUILD-TIPS.txt
index 882ee95..d163d3f 100644
--- a/NT-BUILD-TIPS.txt
+++ b/NT-BUILD-TIPS.txt
@@ -1,3 +1,33 @@
+Compiling RRDtool 1.1.x on Win32 (WinXP/Win2K with Visual C++):
+---------------------------------------------------------------
+4/1/02 Jake Brutlag (jakeb@corp.webtv.net)
+
+These notes share some insight I gained compiling 1.1.x with
+MS Visual C++ 6.0 (using project files). This information may or
+may not be accurate at the time you are reading this.
+
+(1) freetype and rrdtool cannot use precompiled headers (which are
+enabled by default for MSVC++ projects).  MSVC++ 6.0 does not
+support precompiled headers if #include directives contain MACROS.
+(2) Compile Release build with Default optimization, not the
+Maximize Speed optimization. I encountered some strange errors
+(related to argument processing for complex commands like graph--
+perhaps the getopt stuff is too blame) with Maximize Speed.
+(3) libart relies upon config.h (ostensibly generated by the
+configure script-- but of course not on Win32 platforms). ..\..\confignt
+(which contains a static Win32 version of config.h) should be on
+the include path.
+(4) Fonts are located in the %windir%\fonts, so the default font
+is c:\winnt\fonts\cour.ttf.
+
+Currently, to compile rrd.lib and rrdtool.exe using
+the MSVC++ project files, first start MSVC++ 6.0. Open the rrdtool
+workspace (rrdtool.dsw in the src directory). The active project/
+configuration should be rrdtool-Win32 Release. Select Rebuild All
+from the Build menu. The static link library (rrd.lib) will
+be generated in src\release directory and executable will be generated
+in the src\toolrelease directory.
+
 Compiling RRDtool on NT ... work in progress
 ---------------------------------------------------------------
                          by Tamas Kovacshazy (khazy@mit.bme.hu)
@@ -28,7 +58,7 @@ Is a library missing? But it does not stop with an error...
 
 4. nmake test (You must have Visual C++ on the machine!)
 
-After these steps it generates the test files (gifs and rrds),
+After these steps it generates the test files (svgs and rrds),
 and they seem to be good.
 
 The real problem in the shared perl modul is the following: