Warning fix for eVC4 build.

[wxWidgets.git] / docs / msw / install.txt

diff --git a/docs/msw/install.txt b/docs/msw/install.txt
index 3eb302052ca987173cc52695d8c782315941ccc7..2ecc84b31bc977c4ac1454ab286352b2fc96cf42 100644 (file)
--- a/docs/msw/install.txt
+++ b/docs/msw/install.txt
@@ -1,7 +1,7 @@
-Installing wxWidgets 2.7.0
+Installing wxWidgets 2.8.0

 -----------------------------------------------------------
 
 -----------------------------------------------------------
 

-This is wxWidgets 2.7.0 for Microsoft Windows 9x/ME, Windows NT,
+This is wxWidgets 2.8.0 for Microsoft Windows 9x/ME, Windows NT,

 Windows 2000, Windows XP and Windows CE.
 
 These installation notes can be found in docs/msw/install.txt
 Windows 2000, Windows XP and Windows CE.
 
 These installation notes can be found in docs/msw/install.txt


@@ -133,13 +133,16 @@ Using project files (VC++ 6 and later):
    to compile it.  It will also produce similar variations on jpeg.lib,
    png.lib, tiff.lib, zlib.lib, and regex.lib.
 
    to compile it.  It will also produce similar variations on jpeg.lib,
    png.lib, tiff.lib, zlib.lib, and regex.lib.
 

-   If you want to build DLLs, you have to either build them one by one in
-   proper order (jpeg, png, tiff, zlib, regex, expat, base, core, the rest
-   in any order) or to use wx_dll.dsw workspace which has correct dependencies.
-   Unfortunately, VC++ 6 (but not VC++ 7 and later) doesn't always respect the
-   dependencies among the projects so you may still get linking errors due to
-   wrong build order. If this happens, please just start the build again and
-   eventually all the libraries will be built.
+   If you want to build DLL configurations in wx.dsw project you unfortunately
+   need to build them in the proper order (jpeg, png, tiff, zlib, regex, expat,
+   base, net, odbc, core, gl, html, media, qa, adv, dbgrid, xrc, aui, richtext)
+   manually because VC6 doesn't always respect the correct build order.
+
+   Alternatively, use the special wx_dll.dsw project which adds the
+   dependencies to force the correct order (but, because of this, doesn't work
+   for the static libraries) or simply redo the build several times until all
+   DLLs are linked correctly. Pleae notice that it's normal that dbgrid project
+   doesn't build if wxUSE_ODBC is set to 0 (default).

 3. Open a sample project file, choose a configuration such as
    Win32 Debug using Build | Set Active Configuration..., and compile.
    The project files don't use precompiled headers, to save disk
 3. Open a sample project file, choose a configuration such as
    Win32 Debug using Build | Set Active Configuration..., and compile.
    The project files don't use precompiled headers, to save disk


@@ -344,6 +347,13 @@ Note (4): if Watcom can't read the precompiled header when building a sample,
           try deleting .pch files in build\msw\wat_* and compiling
           the sample again.
 
           try deleting .pch files in build\msw\wat_* and compiling
           the sample again.
 

+Note (5): wxUSE_STD_STRING is disabled in wx/string.h for Watcom as this
+          compiler doesn't come with standard C++ library headers by default.
+          If you install STLPort or another STL implementation, you'll need to
+          edit wx/string.h and remove the check for Digital Mars in it (search
+          for __WATCOM__).
+
+

 Metrowerks CodeWarrior compilation
 ----------------------------------------------------------------
 
 Metrowerks CodeWarrior compilation
 ----------------------------------------------------------------
 


@@ -354,7 +364,7 @@ Metrowerks CodeWarrior compilation
 **       The authoritative list of files is in build/bakefiles/files.bkl
 
 1. CodeWarrior Pro 7 project files in XML format are already
 **       The authoritative list of files is in build/bakefiles/files.bkl
 
 1. CodeWarrior Pro 7 project files in XML format are already

-   included in wxMSW-2.7.0.zip and the setup version.
+   included in wxMSW-2.8.0.zip and the setup version.

 
 2. Review the file include\wx\msw\setup.h (or include\wx\msw\setup0.h if
    you are working from the CVS version) to make sure the settings reflect
 
 2. Review the file include\wx\msw\setup.h (or include\wx\msw\setup0.h if
    you are working from the CVS version) to make sure the settings reflect


@@ -447,9 +457,9 @@ Using makefiles directly
 ----------------------------------------------------------------
 
 NOTE: The makefile.gcc makefiles are for compilation under MinGW using
 ----------------------------------------------------------------
 
 NOTE: The makefile.gcc makefiles are for compilation under MinGW using

-      native make and Windows command interpreter (command.com/cmd.exe), they
-      won't work in other environments (such as UNIX or Unix-like, e.g. MSYS;
-      you have to use configure instead)
+      Windows command interpreter (command.com/cmd.exe), they won't work in
+      other environments (such as UNIX or Unix-like, e.g. MSYS where you have
+      to use configure instead, see the section below)

 
 Here are the steps required using the provided makefiles:
 
 
 Here are the steps required using the provided makefiles:
 


@@ -597,6 +607,12 @@ using bakefile tool according to the instructions in build\bakefiles\README:
     bakefile_gen -f dmars -b ../../samples/minimal/minimal.bkl
 
 
     bakefile_gen -f dmars -b ../../samples/minimal/minimal.bkl
 
 

+Note that wxUSE_STD_STRING is disabled in wx/string.h for Digital Mars as this
+compiler doesn't come with standard C++ library headers by default. If you
+install STLPort or another STL implementation, you'll need to edit wx/string.h
+and remove the check for Digital Mars in it (search for __DMC__).
+
+

 16-bit compilation is no longer supported.
 
 Configuring the build
 16-bit compilation is no longer supported.
 
 Configuring the build