mention comparison operators changes

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

diff --git a/docs/msw/install.txt b/docs/msw/install.txt
index 157388eec8c9c5b82a654cd44f101ce730163a5d..c1b271ce32dcf88ecbe7a6b531fed198da7dd32a 100644 (file)
--- a/docs/msw/install.txt
+++ b/docs/msw/install.txt
@@ -1,7 +1,7 @@
-Installing wxWidgets 2.6.2
+Installing wxWidgets 2.7.0

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

-This is wxWidgets 2.6.2 for Microsoft Windows 9x/ME, Windows NT,
+This is wxWidgets 2.7.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


@@ -132,9 +132,14 @@ Using project files (VC++ 6 and later):
    know you won't need some of the libraries (i.e. html part), you don't have
    to compile it.  It will also produce similar variations on jpeg.lib,
    png.lib, tiff.lib, zlib.lib, and regex.lib.
    know you won't need some of the libraries (i.e. html part), you don't have
    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.
    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.

 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


@@ -261,10 +266,14 @@ If you receive this error add bufferoverflowu.lib to link, e.g.:
 
 See http://support.microsoft.com/?id=894573 for more information.
 
 
 See http://support.microsoft.com/?id=894573 for more information.
 

-Borland C++ 5.0/5.5 compilation
+Borland C++ compilation

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

-Compiling using the makefiles (updated 24 Sept 02):
+The minimum version required is 5.5 (last version supported by BC++ 5.0 was
+2.4.2), which can be downloaded for free from:
+http://www.borland.com/products/downloads/download_cbuilder.html#
+
+Compiling using the makefiles:

 
 1. Change directory to build\msw. Type 'make -f makefile.bcc' to
    make the wxWidgets core library. Ignore the compiler warnings.
 
 1. Change directory to build\msw. Type 'make -f makefile.bcc' to
    make the wxWidgets core library. Ignore the compiler warnings.


@@ -287,11 +296,11 @@ recompile wxWidgets. The same applies if compiling using the IDE.
 Note (3): If you wish debug messages to be sent to the console in
 debug mode, edit makefile.bcc and change /aa to /Tpe in link commands.
 
 Note (3): If you wish debug messages to be sent to the console in
 debug mode, edit makefile.bcc and change /aa to /Tpe in link commands.
 

-Compiling using the IDE files for Borland C++ 5.0: not supported - please
-use version 2.4.1 (using the make utility in commandline mode works fine_
+Cmpilation succeeds with CBuilderX personal edition and CBuilder6, but 
+you may have to copy make.exe from the 5.5 download to the new bin directory.
+Compiling using the IDE files for Borland C++ 5.0 and using CBuilder IDE 
+(v1-v6): not supported 

 
 

-Compiling using CBuilder (v1-v6): not supported - please
-use version 2.4.1 (using the make utility in commandline mode works fine_

 
 ** REMEMBER **
 
 
 ** REMEMBER **
 


@@ -338,8 +347,14 @@ Note (4): if Watcom can't read the precompiled header when building a sample,
 Metrowerks CodeWarrior compilation
 ----------------------------------------------------------------
 
 Metrowerks CodeWarrior compilation
 ----------------------------------------------------------------
 

+** NOTE: We don't use Metrowerks compiler any more and so depend on
+**       your contributions to keep it up to date. It is possible that
+**       the project files mentioned below are out of date due to recently
+**       added files, please add them manually if you get linking errors.
+**       The authoritative list of files is in build/bakefiles/files.bkl
+

 1. CodeWarrior Pro 7 project files in XML format are already
 1. CodeWarrior Pro 7 project files in XML format are already

-   included in wxMSW-2.6.2.zip and the setup version.
+   included in wxMSW-2.7.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


@@ -432,9 +447,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:
 


@@ -474,7 +489,7 @@ For example:
   cd build-debug
   ../configure --with-msw --enable-debug --enable-debug_gdb --disable-shared
   make
   cd build-debug
   ../configure --with-msw --enable-debug --enable-debug_gdb --disable-shared
   make

-  make install % This step is optional, see note (8) below.
+  make install % This step is optional, see note (6) below.

   cd samples/minimal
   make
   ./minimal.exe
   cd samples/minimal
   make
   ./minimal.exe