docs/msw/install.txt

   1
   2 Installing wxWindows 2.0
   3 ------------------------
   4
   5 Unarchiving
   6 -----------
   7
   8 If there is a setup program, run the setup program that comes with the Windows version.
   9 Do not install into a path that contains spaces. The installation program should set the
  10 WXWIN environment variable, which will be activated when your machine is rebooted.
  11
  12 If there is no setup program, it will come as a series of .zip
  13 files:
  14
  15 wx200gen.zip            Generic source code and samples (required)
  16 wx200msw.zip            Windows-specific source code and samples (required)
  17 wx200doc.zip            Documentation source code (not required)
  18 wx200hlp.zip            WinHelp documentation
  19 wx200pdf.zip            Acrobat PDF documentation
  20 wx200htm.zip            HTML documentation
  21 wx200vc.zip             MS VC++ 5.0 project files
  22 wx200cw.zip             Metrowerks CodeWarrior project files
  23
  24 Unarchive the required files plus any optional documentation
  25 files into a suitable directory such as c:\wx. Alter your
  26 WXWIN environment variable to point to this directory.
  27
  28 Compilation
  29 -----------
  30
  31 At present, wxWindows compiles with VC++ 4.0/5.0/6.0,
  32 BC++ 4.5/5.0, Gnu-Win32 b19/b20, and Mingw32. It may compile
  33 with 16-bit compilers (BC++ and VC++ 1.5) but this hasn't
  34 been tested lately.
  35
  36 Visual C++ 4.0/5.0/6.0 compilation
  37 ----------------------------------
  38
  39 Using project files:
  40
  41 1. Unarchive wx200vc.zip, the VC++ 5 project makefiles.
  42 2. Open src/wxvc.dsp, set Debug or Release configuration, and
  43    compile. This will produce lib/wxvc.lib or lib/wxvc_debug.lib.
  44 3. Open a sample project file, choose a configuration, and compile.
  45    The project files don't use precompiled headers, to save
  46    space, but you can switch PCH compiling on for greater speed.
  47
  48 Using makefiles:
  49
  50 1. Make sure your WXWIN variable is set.
  51 2. Change directory to wx\src\msw. Type 'nmake -f makefile.nt' to
  52    make the wxWindows core library.
  53 3. Change directory to wx\samples and type 'nmake -f makefile.nt'
  54    to make all the samples. You can also make them individually.
  55
  56 Notes: if you wish to use templates, please edit
  57 include\wx\msw\setup.h and set wxUSE_DEBUG_NEW_ALWAYS to 0.
  58 Without this, the redefinition of 'new' will cause problems in
  59 the headers. Alternatively, #undef new before including template headers.
  60
  61 Visual C++ 1.5 compilation
  62 --------------------------
  63
  64 1. Make sure your WXWIN variable is set, and uses the FAT (short
  65    name) form.
  66 2. Change directory to wx\src\msw. Type 'nmake -f makefile.dos' to
  67    make the wxWindows core library.
  68 3. Change directory to a sample, such as wx\samples\minimal, and
  69    type 'nmake -f makefile.dos'.
  70
  71 Borland C++ 4.5/5.0 compilation
  72 -------------------------------
  73
  74 1. Make sure your WXWIN variable is set, and uses the FAT (short
  75    name) form if doing a 16-bit compile.
  76 2. Change directory to wx\src\msw. Type 'make -f makefile.b32' to
  77    make the wxWindows core library. Ignore the warnings about
  78    'XXX' not found in library.
  79 3. Change directory to a sample such as minimal, and type
  80   'make -f makefile.b32'.
  81 4. For release versions, recompile wxWindows and samples using
  82    'make -f makefile.b32 clean'
  83    'make -f makefile.b32 FINAL=1'
  84    for the library and samples.
  85
  86 Note: the wxWindows library and (some) samples compile in 16-bit mode
  87 using makefile.bcc, but at present the wxWindows resource system is switched
  88 off in this mode. See issues.txt for details.
  89
  90 Borland C++Builder compilation
  91 ------------------------------
  92
  93 C++Builder compilation is the same as for Borland C++ above.
  94 It has only been tested with C++Builder 1.0 so far, and no
  95 project files are currently supplied.
  96
  97 Watcom C++ 10.6 compilation
  98 ---------------------------
  99
 100 Currently under construction, but so far we have:
 101
 102 1. Make sure your WXWIN variable is set, and uses the FAT (short
 103    name) form.
 104 2. Change directory to wx\src\msw. Type 'wmake -f makefile.wat' to
 105    make the wxWindows core library.
 106 3. Change directory to wx\samples\minimal and type 'wmake -f makefile.wat'
 107    to make this sample. There are a lot of link errors at this
 108    point, so can anyone help work out what I've done wrong?
 109
 110 Metrowerks CodeWarrior compilation
 111 ----------------------------------
 112
 113 1. Downloaded and unzip wx200cw.zip.
 114 2. Load the make_cw.mcp project in wx\src, and compile.
 115 3. Load the make_cw.mcp project in wx\samples\minimal, and compile.
 116    Further project files for samples will be available in due
 117    course.
 118
 119 Gnu-Win32 b19/b20/Mingw32 compilation
 120 -------------------------------------
 121
 122 wxWindows 2.0 supports Gnu-Win32/Cygwin b19, b20, Mingw32, and Mingw32/EGCS.
 123
 124 Thanks are due to Keith Garry Boyce (garp@opustel.com) and Cygnus for making
 125 it all possible.
 126
 127 From wxWindows 2.0 beta 9, both Gnu-Win32 and Mingw32 (the minimal
 128 distribution of Gnu-Win32) can be used with the same makefiles.
 129
 130 Here are the steps required:
 131
 132 - Retrieve and install the latest beta of Gnu-Win32, or Mingw32, as per the
 133   instructions with either of these packages.
 134
 135 - If using Mingw32 (including the EGCS variant), you need some
 136   extra files to use the wxWindows makefiles. You can find these
 137   files in ports/mingw32 on the ftp site or CD-ROM, as extra.zip.
 138   These should be extracted to the Mingw32 directory.
 139   IMPORTANT: also see mingw32.txt in this directory (docs/msw)
 140   about a fix that has to be applied to a Mingw32 header file.
 141
 142 - Modify the file wx/src/cygnus.bat (or mingw32.bat or mingegcs.bat)
 143   to set up appropriate variables, if necessary mounting drives.
 144   Run it before compiling.
 145
 146 - For Gnu-Win32, make sure there's a \tmp directory on your
 147   Windows drive or bison will crash.
 148
 149 - Edit wx/src/makeg95.env and search for MINGW32. Take note of
 150   the comments for adjusting settings to suit Gnu-Win32 or
 151   Mingw32. Basically, this is just a case of adding the __MINGW32__ symbol
 152   to OPTIONS for Mingw32, or removing it for Cygnus Gnu-Win32.
 153   For Mingw32/EGCS, add both __MINGW32__ and __EGCS__.
 154
 155 - Mingw32 may not support winsock.h, so comment out
 156   socket-related files in src/msw/makefile.g95.
 157
 158 - Use the makefile.g95 files for compiling wxWindows and samples,
 159   e.g.:
 160   > cd c:\wx\src\msw
 161   > make -f makefile.g95
 162   > cd c:\wx\samples\minimal
 163   > make -f makefile.g95
 164
 165 - Use the 'strip' command to reduce executable size.
 166
 167 - With Cygnus Gnu-Win32, you can invoke gdb --nw myfile.exe to
 168   debug an executable. If there are memory leaks, they will be
 169   flagged when the program quits.
 170
 171 - If using GnuWin32 b18, you will need to copy windres.exe
 172   from e.g. the Mingw32 distribution, to a directory in your path.
 173
 174 All targets have 'clean' targets to allow removal of object files
 175 and other intermediate compiler files.
 176
 177 Gotchas:
 178
 179 - libwx.a is 48 MB or more - but much less if compiled with no
 180   debug info (-g0) and level 4 optimization (-O4).
 181 - install.exe doesn't have built-in decompression because lzexpand.lib
 182   isn't available with Gnu-Win32. However, you can use it with external
 183   decompression utilities.
 184 - Doesn't compile src/msw/ole files, so no drag and drop.
 185
 186 References:
 187
 188  - The GNU-WIN32 site is at
 189      http://www.cygnus.com/gnu-win32/
 190  - Mingw32 is available at:
 191      http://agnes.dida.physik.uni-essen.de/~janjaap/mingw32/index.html
 192  - See also http://web.ukonline.co.uk/julian.smart/wxwin/gnuwin32.htm
 193
 194 Notes
 195 -----
 196
 197 - Debugging: under Windows 95, debugging output isn't output in
 198   the same way that it is under NT or Windows 3.1. Set
 199   wxUSE_DBWIN32 to 1 if you wish to enable code to output debugging
 200   info to an external debug monitor, such as Andrew Tucker's DBWIN32.
 201   You can download DBWIN32 from:
 202
 203         http://ftp.digital.com/pub/micro/NT/WinSite/programr/dbwin32.zip
 204
 205   and it's also on the wxWindows CD-ROM under Packages.
 206