X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/025e88c50bc838a02e352cdeb53918ebbec20aee..f3033278722328d37b98406b45060a2a3b8b1877:/docs/msw/install.txt diff --git a/docs/msw/install.txt b/docs/msw/install.txt index 8a514b029b..ee25d87c26 100644 --- a/docs/msw/install.txt +++ b/docs/msw/install.txt @@ -25,11 +25,18 @@ Unarchive the required files plus any optional documentation files into a suitable directory such as c:\wx. Alter your WXWIN environment variable to point to this directory. +Other add-on packages are available from the wxWindows Web site, such as: + +- glcanvas.zip. Use OpenGL in a wxWindows window. +- ogl3.zip. Object Graphics Library: build network diagrams, CASE tools etc. +- tex2rtf3.zip. Tex2RTF: create Windows Help, HTML, and Word RTF files from + the same document source. + Compilation ----------- At present, wxWindows compiles with VC++ 4.0/5.0/6.0, -BC++ 4.5/5.0, Gnu-Win32 b19/b20, and Mingw32. It may compile +BC++ 4.5/5.0, Cygwin b19/b20, and Mingw32. It may compile with 16-bit compilers (BC++ and VC++ 1.5) but this hasn't been tested lately. @@ -48,16 +55,33 @@ Using project files: Using makefiles: 1. Make sure your WXWIN variable is set. -2. Change directory to wx\src\msw. Type 'nmake -f makefile.nt' to +2. Change directory to wx\src\msw. Type 'nmake -f makefile.vc' to make the wxWindows core library. -3. Change directory to wx\samples and type 'nmake -f makefile.nt' +3. Change directory to wx\samples and type 'nmake -f makefile.vc' to make all the samples. You can also make them individually. -Notes: if you wish to use templates, please edit +To build the release version using makefiles, add FINAL=1 to your +nmake invocation, both when building the library and for samples. + +Use the 'clean' target to clean all objects, libraries and +executables. + +To build the DLL version using makefiles: + +1. Change directory to wx\src\msw. Type 'nmake -f makefile.vc dll pch' + to make both a suitable DLL and import library, and to build a + suitable precompiled header file for compiling applications. +2. Invoke a sample makefile with 'nmake -f makefile.vc WXUSINGDLL=1'. + +Note (1): if you wish to use templates, please edit include\wx\msw\setup.h and set wxUSE_DEBUG_NEW_ALWAYS to 0. Without this, the redefinition of 'new' will cause problems in the headers. Alternatively, #undef new before including template headers. +Note (2): libraries and applications generated with makefiles and +project files are unlikely to be compatible, so use one method or +the other. + Visual C++ 1.5 compilation -------------------------- @@ -68,6 +92,12 @@ Visual C++ 1.5 compilation 3. Change directory to a sample, such as wx\samples\minimal, and type 'nmake -f makefile.dos'. +Add FINAL=1 to your makefile invocation to build the release +versions of the library and samples. + +Use the 'clean' target to clean all objects, libraries and +executables. + Borland C++ 4.5/5.0 compilation ------------------------------- @@ -78,23 +108,32 @@ Borland C++ 4.5/5.0 compilation 'XXX' not found in library. 3. Change directory to a sample such as minimal, and type 'make -f makefile.b32'. +4. For release versions, recompile wxWindows and samples using + 'make -f makefile.b32 clean' + 'make -f makefile.b32 FINAL=1' + for the library and samples. Note: the wxWindows library and (some) samples compile in 16-bit mode using makefile.bcc, but at present the wxWindows resource system is switched off in this mode. See issues.txt for details. +Borland C++Builder compilation +------------------------------ + +C++Builder compilation is the same as for Borland C++ above. + +Tested with C++Builder 1.0 and 3.0. Only makefiles are currently +supplied. + Watcom C++ 10.6 compilation --------------------------- -Currently under construction, but so far we have: - 1. Make sure your WXWIN variable is set, and uses the FAT (short name) form. 2. Change directory to wx\src\msw. Type 'wmake -f makefile.wat' to make the wxWindows core library. 3. Change directory to wx\samples\minimal and type 'wmake -f makefile.wat' - to make this sample. There are a lot of link errors at this - point, so can anyone help work out what I've done wrong? + to make this sample. Metrowerks CodeWarrior compilation ---------------------------------- @@ -105,26 +144,73 @@ Metrowerks CodeWarrior compilation Further project files for samples will be available in due course. -Gnu-Win32 b19/b20/Mingw32 compilation -------------------------------------- +NOTES: + +(a) Unfortunately CodeWarrior support is broken in this +release. Stefan Csomor (csomor@advancedconcepts.ch) will rectify this shortly. +(b) You need CodeWarrior Pro 4 plus the patches to 4.1 from the +Metrowerks Web site. + +Symantec C++ compilation +------------------------ + +1. Make sure your WXWIN variable is set, and uses the FAT (short + name) form. +2. Edit setup.h and set wxUSE_DRAG_AND_DROP to 0. +3. Change directory to wx\src\msw. Type 'make -f makefile.sc' to + make the wxWindows core library. +4. Change directory to wx\samples\minimal and type 'make -f makefile.sc' + to make this sample. + +Note: the minimal sample doesn't link properly ('Error: no +start address'). +32-bit compilation only (partially) supported at present, using SC++ 6.1. +Some functionality is missing using this compiler (see makefile). +Add -D__WIN95__ if your SC++ has Windows 95 support, and ignore +Step (2). 16-bit compilation is left as an excercise for the user! + +Salford C++ compilation +----------------------- + +1. Make sure your WXWIN variable is set, and uses the FAT (short + name) form. +2. Edit SALFORDDIR and RESOURCEDIR in src/makesl.env as per + notes. +3. Change directory to wx\src\msw. Type 'mk32 -f makefile.sl all' to + make the wxWindows core library. +4. Change directory to wx\samples\minimal and type 'mk32 -f makefile.sl' + to make this sample. -wxWindows 2.0 supports Gnu-Win32/Cygwin b19, b20, Mingw32, and Mingw32/EGCS. +Unfortunately, Salford C++ seems to have problems with its code generation for +operations on objects, as seen in wxFrame::OnMenuHighlight +(minimal sample) or wxWindow::SetValidator (mdi sample). Also the +the debugging version of the library is 90MB, with samples coming in +at 40MB :-) However, wxWindows at least makes a good test suite for +improving the compiler. + +Cygwin b19/b20/Mingw32 compilation +---------------------------------- + +wxWindows 2.0 supports Cygwin (formerly GnuWin32) b19, b20, Mingw32, and Mingw32/EGCS. Thanks are due to Keith Garry Boyce (garp@opustel.com) and Cygnus for making it all possible. -From wxWindows 2.0 beta 9, both Gnu-Win32 and Mingw32 (the minimal -distribution of Gnu-Win32) can be used with the same makefiles. +From wxWindows 2.0 beta 9, both Cygwin and Mingw32 (the minimal +distribution of Cygwin) can be used with the same makefiles. Here are the steps required: -- Retrieve and install the latest beta of Gnu-Win32, or Mingw32, as per the +- Retrieve and install the latest beta of Cygwin, or Mingw32, as per the instructions with either of these packages. - If using Mingw32 (including the EGCS variant), you need some extra files to use the wxWindows makefiles. You can find these files in ports/mingw32 on the ftp site or CD-ROM, as extra.zip. These should be extracted to the Mingw32 directory. + If you have already have downloaded bison, flex, make, rm, mv + from elsewhere, you won't need this. + IMPORTANT: also see mingw32.txt in this directory (docs/msw) about a fix that has to be applied to a Mingw32 header file. @@ -132,14 +218,16 @@ Here are the steps required: to set up appropriate variables, if necessary mounting drives. Run it before compiling. -- For Gnu-Win32, make sure there's a \tmp directory on your +- For Cygwin, make sure there's a \tmp directory on your Windows drive or bison will crash. - Edit wx/src/makeg95.env and search for MINGW32. Take note of - the comments for adjusting settings to suit Gnu-Win32 or + the comments for adjusting settings to suit Cygwin or Mingw32. Basically, this is just a case of adding the __MINGW32__ symbol - to OPTIONS for Mingw32, or removing it for Cygnus Gnu-Win32. + to OPTIONS for Mingw32, or removing it for Cygnus Cygwin. For Mingw32/EGCS, add both __MINGW32__ and __EGCS__. + You may need to remove -loldnames from WINLIBS for Mingw32, or add it for + Cygwin. - Mingw32 may not support winsock.h, so comment out socket-related files in src/msw/makefile.g95. @@ -153,7 +241,7 @@ Here are the steps required: - Use the 'strip' command to reduce executable size. -- With Cygnus Gnu-Win32, you can invoke gdb --nw myfile.exe to +- With Cygnus Cygwin, you can invoke gdb --nw myfile.exe to debug an executable. If there are memory leaks, they will be flagged when the program quits. @@ -168,7 +256,7 @@ Gotchas: - libwx.a is 48 MB or more - but much less if compiled with no debug info (-g0) and level 4 optimization (-O4). - install.exe doesn't have built-in decompression because lzexpand.lib - isn't available with Gnu-Win32. However, you can use it with external + isn't available with Cygwin. However, you can use it with external decompression utilities. - Doesn't compile src/msw/ole files, so no drag and drop. @@ -180,8 +268,23 @@ References: http://agnes.dida.physik.uni-essen.de/~janjaap/mingw32/index.html - See also http://web.ukonline.co.uk/julian.smart/wxwin/gnuwin32.htm -Notes ------ +TWIN32 and gcc on Linux +----------------------- + +The wxWindows 2 for Windows port may be compiled using +the TWIN32 emulator package from www.willows.com. However, +TWIN32 is by no means finished so this should be taken as +something to think about for the future, rather than +a tool for writing products with. + +Use makefile.twn in much the same way as makefile.g95, as +described above. Not all sample makefiles are supplied yet. + +For some reason, I found I had to copy TWIN32's Windows resource +compiler (rc) to the current working directory for it to be found. + +General Notes +------------- - Debugging: under Windows 95, debugging output isn't output in the same way that it is under NT or Windows 3.1. Set @@ -193,3 +296,7 @@ Notes and it's also on the wxWindows CD-ROM under Packages. +- If you are installing wxWindows 2 from CVS, you may find that + include/wx/msw/setup.h is missing. This is deliberate, to avoid + developers' different setup.h configurations getting confused. + Please copy setup0.h to setup.h before compiling.