Rebake after bakefile changes.

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

diff --git a/docs/msw/install.txt b/docs/msw/install.txt
index bd0c5c276900561442506a6915824346e02d2e47..77054b6db704aee4387e53183fb7974eb2845332 100644 (file)
--- a/docs/msw/install.txt
+++ b/docs/msw/install.txt
@@ -9,15 +9,20 @@ in your wxWidgets distribution.
 
 IMPORTANT NOTE: If you experience problems installing, please
 re-read this instructions and other related files (changes.txt,
 
 IMPORTANT NOTE: If you experience problems installing, please
 re-read this instructions and other related files (changes.txt,

-readme.txt, FAQ) carefully before mailing wx-users. Preferably,
-try to fix the problem first and then upload a patch to
-SourceForge:
+readme.txt, FAQ) carefully before posting to wx-users list.

 
 

-  http://sourceforge.net/patch/?group_id=9863
+If you are sure that you found a bug, please report it at
+wxWidgets Trac:

 
 

-Please report bugs using the SourceForge bug tracker:
+  http://trac.wxwidgets.org/newticket
+
+Please notice that often trying to correct the bug yourself is the
+quickest way to fix it. Even if you fail to do it, you may
+discover valuable information allowing us to fix it while doing
+it. We also give much higher priority to bug reports with patches
+fixing the problems so this ensures that your report will be
+addressed sooner.

 
 

-  http://sourceforge.net/bugs/?group_id=9863

 
 Unarchiving
 ============================================================
 
 Unarchiving
 ============================================================


@@ -96,7 +101,7 @@ Their Unicode debug counterparts in wxUniversal build would be
   wxmswuniv29ud_adv.lib
 
 These directories also contain subdirectory with wx/setup.h header. This
   wxmswuniv29ud_adv.lib
 
 These directories also contain subdirectory with wx/setup.h header. This

-subdirectory is named after port, Unicode, wxUniv and debug settings and 
+subdirectory is named after port, Unicode, wxUniv and debug settings and

 you must add it to include paths when compiling your application. Some
 examples:
 
 you must add it to include paths when compiling your application. Some
 examples:
 


@@ -135,8 +140,8 @@ Using project files (VC++ 6 and later):
 
    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,
 
    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.
+   base, net, odbc, core, gl, html, media, qa, adv, dbgrid, xrc, aui, richtext,
+   propgrid) 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
 
    Alternatively, use the special wx_dll.dsw project which adds the
    dependencies to force the correct order (but, because of this, doesn't work


@@ -276,8 +281,8 @@ 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
 
 2.4.2), which can be downloaded for free from:
 http://www.borland.com/products/downloads/download_cbuilder.html
 

-We have found that the free Turbo Explorer and commercial BDS work fine; the 
-debugger is very good. To avoid linker errors you will need to add 
+We have found that the free Turbo Explorer and commercial BDS work fine; the
+debugger is very good. To avoid linker errors you will need to add

 -DSHARED=1 to the makefile line for the library
 
 The version 5.6 included in Borland C++ Builder 2006 works as well after the
 -DSHARED=1 to the makefile line for the library
 
 The version 5.6 included in Borland C++ Builder 2006 works as well after the


@@ -291,7 +296,7 @@ Compiling using the makefiles:
    This produces a couple of libraries in the lib\bcc_lib directory.
 
 2. Change directory to a sample or demo such as samples\minimal, and type
    This produces a couple of libraries in the lib\bcc_lib directory.
 
 2. Change directory to a sample or demo such as samples\minimal, and type

-  'make -f makefile.bcc'. This produces a windows exe file - by default 
+  'make -f makefile.bcc'. This produces a windows exe file - by default

    in the bcc_mswd subdirectory.
 
 Note (1): the wxWidgets makefiles assume dword structure alignment. Please
    in the bcc_mswd subdirectory.
 
 Note (1): the wxWidgets makefiles assume dword structure alignment. Please


@@ -311,7 +316,7 @@ Using the Debugger and IDE in BDS or Turbo Explorer
 ---------------------------------------------------
 
 
 ---------------------------------------------------
 
 

-Doubleclick / open samples\minimal\borland.bdsproj. The current version 
+Doubleclick / open samples\minimal\borland.bdsproj. The current version

 is to be used with a dynamic build of wxWidgets-made by running
 make -f Makefile.bcc -DBUILD=debug -DSHARED=1
 in wxWidgets\build\msw. You also need the wxWidgets\lib\bcc_dll
 is to be used with a dynamic build of wxWidgets-made by running
 make -f Makefile.bcc -DBUILD=debug -DSHARED=1
 in wxWidgets\build\msw. You also need the wxWidgets\lib\bcc_dll


@@ -322,11 +327,11 @@ To use this to debug other samples, copy the borland_ide.cpp
 and borland.bdsproj files, then replace all occurences of
 "minimal" with the name of the new project files
 
 and borland.bdsproj files, then replace all occurences of
 "minimal" with the name of the new project files
 

-Compilation succeeds with CBuilderX personal edition and CBuilder6, but 
+Compilation 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.
 
 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 the IDE files for Borland C++ 5.0 and using CBuilder IDE
+(v1-v6): not supported

 
 
 
 
 
 


@@ -486,23 +491,20 @@ NOTE: The makefile.gcc makefiles are for compilation under MinGW using
       other environments (such as UNIX or Unix-like, e.g. MSYS where you have
       to use configure instead, see the section below)
 
       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:
-
-- If you are using gcc-2.95, edit build\msw\config.gcc and set the GCC_VERSION
-  variable to "2.95".
-
-- Use the makefile.gcc files for compiling wxWidgets and samples,
-  e.g. to compile a debugging version of wxWidgets:
+Use the makefile.gcc files for compiling wxWidgets and samples,
+e.g. to compile a debugging version of wxWidgets:

   > cd c:\wx\build\msw
   > cd c:\wx\build\msw

-  > make -f makefile.gcc BUILD=debug
+  > mingw32-make -f makefile.gcc BUILD=debug

   > cd c:\wx\samples\minimal
   > cd c:\wx\samples\minimal

-  > make -f makefile.gcc BUILD=debug
+  > mingw32-make -f makefile.gcc BUILD=debug

   (See below for more options.)
 
   (See below for more options.)
 

-  Ignore the warning about the default entry point.
+Notice that Windows command interpreter (cmd.exe) and mingw32-make must be
+used, using Bash (sh.exe) and make.exe from MSYS will only work when using
+configure-based build procedure described below!

 
 

-- Use the 'strip' command to reduce executable/dll size (note that
-  stripping an executable/dll will remove debug information!).
+You can also use the 'strip' command to reduce executable/dll size (note that
+stripping an executable/dll will remove debug information!).

 
 All targets have 'clean' targets to allow removal of object files
 and other intermediate compiler files.
 
 All targets have 'clean' targets to allow removal of object files
 and other intermediate compiler files.


@@ -610,7 +612,7 @@ Symantec & DigitalMars C++ compilation
 
 The DigitalMars compiler is a free succssor to the Symantec compiler
 and can be downloaded from http://www.digitalmars.com/
 
 The DigitalMars compiler is a free succssor to the Symantec compiler
 and can be downloaded from http://www.digitalmars.com/

-   
+

 1. You need to download and unzip in turn (later packages will overwrite
    older files)
       Digital Mars C/C++ Compiler Version 8.40 or later
 1. You need to download and unzip in turn (later packages will overwrite
    older files)
       Digital Mars C/C++ Compiler Version 8.40 or later


@@ -697,9 +699,9 @@ Basic options
 ----------------------------------------------------------------
 
 BUILD=release
 ----------------------------------------------------------------
 
 BUILD=release

-  Builds release version of the library. It differs from default 'debug' 
+  Builds release version of the library. It differs from default 'debug'

   in lack of appended 'd' in name of library, does not define __WXDEBUG__
   in lack of appended 'd' in name of library, does not define __WXDEBUG__

-  and not include debug information compiled into object files and the 
+  and not include debug information compiled into object files and the

   executable.
 
 SHARED=1
   executable.
 
 SHARED=1


@@ -722,7 +724,7 @@ Advanced options
 ----------------------------------------------------------------
 
 MONOLITHIC=1
 ----------------------------------------------------------------
 
 MONOLITHIC=1

-  Starting with version 2.5.1, wxWidgets has the ability to be built as 
+  Starting with version 2.5.1, wxWidgets has the ability to be built as

   several smaller libraries instead of single big one as used to be the case
   in 2.4 and older versions. This is called "multilib build" and is the
   default behaviour of makefiles. You can still build single library
   several smaller libraries instead of single big one as used to be the case
   in 2.4 and older versions. This is called "multilib build" and is the
   default behaviour of makefiles. You can still build single library


@@ -814,7 +816,7 @@ Compiler specific options
 * MinGW
 
 If you are using gcc-2.95 instead of gcc3, you must set GCC_VERSION to
 * MinGW
 
 If you are using gcc-2.95 instead of gcc3, you must set GCC_VERSION to

-2.95. In build\msw\config.gcc, change 
+2.95. In build\msw\config.gcc, change

 > GCC_VERSION = 3
 to
 > GCC_VERSION = 2.95
 > GCC_VERSION = 3
 to
 > GCC_VERSION = 2.95


@@ -850,7 +852,7 @@ compiler name. Examples of directory names:
   build\msw\bcc_mswunivd       SHARED=0, WXUNIV=1, BUILD=debug
   build\msw\vc_mswunivd        ditto, with Visual C++
 
   build\msw\bcc_mswunivd       SHARED=0, WXUNIV=1, BUILD=debug
   build\msw\vc_mswunivd        ditto, with Visual C++
 

-Libraries and DLLs are copied into subdirectory of lib directory with 
+Libraries and DLLs are copied into subdirectory of lib directory with

 name derived from compiler and static/DLL setting and setup.h into directory
 with name that contains other settings:
 
 name derived from compiler and static/DLL setting and setup.h into directory
 with name that contains other settings:
 


@@ -871,7 +873,7 @@ to setup.h, you should do them in this file, _not_ in include\wx\msw\setup.h.
 
 If you set CFG to something, the value is appended to directory names. E.g.
 for CFG=MyBuild, you'll have object files in
 
 If you set CFG to something, the value is appended to directory names. E.g.
 for CFG=MyBuild, you'll have object files in

-  
+

   build\msw\bcc_mswMyBuild
   build\msw\bcc_mswdllMyBuild
   etc.
   build\msw\bcc_mswMyBuild
   build\msw\bcc_mswdllMyBuild
   etc.


@@ -883,7 +885,7 @@ and libraries in
   etc.
 
 By now it is clear what CFG is for: builds with different CFG settings don't
   etc.
 
 By now it is clear what CFG is for: builds with different CFG settings don't

-share any files and they use different setup.h files. This allows you to e.g. 
+share any files and they use different setup.h files. This allows you to e.g.

 have two static debug builds, one with wxUSE_SOCKETS=0 and one with sockets
 enabled (without CFG, both of them would be put into same directory and there
 would be conflicts between the files).
 have two static debug builds, one with wxUSE_SOCKETS=0 and one with sockets
 enabled (without CFG, both of them would be put into same directory and there
 would be conflicts between the files).