X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/025e88c50bc838a02e352cdeb53918ebbec20aee..75ce0581545a6c151484e488596ed200c2ffd93e:/docs/msw/install.txt diff --git a/docs/msw/install.txt b/docs/msw/install.txt index 8a514b029b..6cb0f70a7a 100644 --- a/docs/msw/install.txt +++ b/docs/msw/install.txt @@ -48,16 +48,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 +85,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 +101,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,6 +137,43 @@ Metrowerks CodeWarrior compilation Further project files for samples will be available in due course. +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. + +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. + Gnu-Win32 b19/b20/Mingw32 compilation ------------------------------------- @@ -180,6 +249,18 @@ References: http://agnes.dida.physik.uni-essen.de/~janjaap/mingw32/index.html - See also http://web.ukonline.co.uk/julian.smart/wxwin/gnuwin32.htm +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. + Notes -----