X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/f6bcfd974ef26faf6f91a62cac09827e09463fd1..6a54cc2a1156229f1db27ec816c9be84e8da2ee3:/docs/msw/install.txt?ds=sidebyside diff --git a/docs/msw/install.txt b/docs/msw/install.txt index 279aab16a4..138ee16b0a 100644 --- a/docs/msw/install.txt +++ b/docs/msw/install.txt @@ -1,9 +1,9 @@ -Installing wxWindows 2.2 +Installing wxWindows 2.3 ------------------------ -This is wxWindows 2.2 for Microsoft Windows 3.1, 95, 98 and -Windows NT/Windows 2000. This is an official, stable release. +This is wxWindows 2.3 for Microsoft Windows 3.1, 95, 98 and +Windows NT/Windows 2000. This is an unstable development release. IMPORTANT NOTE: If you experience problems installing, please re-read this instructions and other related files (changes.txt, @@ -288,7 +288,7 @@ samples, and not all samples. The remaining samples can be made with the makefiles. See also the demos hierarchy which doesn't have any BC++ project files yet. -Note (2): to make the png, xpm, zlib, jpeg and tiff libraries (needed for +Note (2): to make the png, zlib, jpeg and tiff libraries (needed for some samples) you need to compile them with bc32.ide. Note (3): the debug version of the wxWindows library is about 40 MB, and the @@ -309,7 +309,7 @@ issues concerning the compiler installation: 2. Make sure that you downloaded and installed the service pack 1 for Borland C++ 5.5. This SP1 can be downloaded from: - http://www.borland.com/devsupport/bcppbuilder/file_supplements.html + http://www.borland.com/devsupport/bcppbuilder/patches/#freecompiler55 IMPORTANT: When installing SP1, make sure that you extract (UnZip) the files @@ -412,15 +412,6 @@ Watcom C++. Note (3): if Watcom can't read the precompiled header when building a sample, try deleting src\msw\watcom.pch and compiling the sample again. -Note (4): if you get _popen_ and _pclose_ link errors, try -recompiling wxWindows with XPM support disabled in setup.h. -Alternatively, make sure these lines exist at the top of -src\xpm\xpmi.h: - -// Added by JACS for Watcom C++/wxWindows compilation (no popen/pclose functions) -#ifdef __WATCOMC__ -#define NO_ZPIPE -#endif Metrowerks CodeWarrior compilation ---------------------------------- @@ -474,14 +465,14 @@ 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 +Cygwin/Mingw32 compilation ---------------------------------- -wxWindows 2 supports Cygwin (formerly GnuWin32) b19, b20, Mingw32, -and Mingw32/EGCS. Cygwin 1.1.0 and 1.1.1 are not yet supported. +wxWindows 2 supports Cygwin (formerly GnuWin32) betas and +releases, and Mingw32. -Thanks are due to Keith Garry Boyce (garp@opustel.com) and Cygnus for making -it all possible. +Thanks are due to Keith Garry Boyce (garp@opustel.com), Cygnus +and others for making it all possible. Both Cygwin and Mingw32 (the minimal distribution of Cygwin) can be used with the same makefiles. @@ -491,11 +482,10 @@ Here are the steps required: - 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 alread downloaded bison, flex, make, rm, cp, mv +- If using Mingw32, you need some extra files to use the wxWindows + makefiles. You can find these files in ports/mingw32 on the + wxWindows ftp site or CD-ROM, as extra.zip. These should be extracted + to the Mingw32 directory. If you have alread downloaded rm, cp, mv from elsewhere, you won't need this. If using Mingw32 2.95 and below with wxWindows 2.1 or above, you @@ -508,15 +498,14 @@ Here are the steps required: Run it before compiling. - For Cygwin, make sure there's a \tmp directory on your - Windows drive or bison will crash (actually you don't need this - for ordinary wxWindows compilation: a pre-generated .c file is + Windows drive or bison will crash (actually you don't need + bison for ordinary wxWindows compilation: a pre-generated .c file is supplied). - Edit wx/src/makeg95.env and set the MINGW32 variable at the top of - the file to either 1 (you have Mingw32) or 0 (you have Cygwin32). - If using MINGW32, also set the MINGW32VERSION variable - appropriately. Note: Cygwin 1.1.0 and above may - need MINGW32 set to 1 to compile properly. + the file to either 1 (you have Mingw32 or Cygwin 1.x releases) or 0 + (if you have Cygwin betas). If using Mingw32, also set the + MINGW32VERSION variable appropriately. - Set your WXWIN variable to where wxWindows is installed. *** IMPORTANT: For Cygwin/Mingw32, use forward slashes in the path, not @@ -533,7 +522,7 @@ Here are the steps required: - Use the 'strip' command to reduce executable size. -- With Cygnus Cygwin, you can invoke gdb --nw myfile.exe to +- With 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. @@ -585,11 +574,10 @@ Notes: References: - - The GNU-WIN32 site is at - http://www.cygnus.com/gnu-win32/ + - The Cygwin site is at + http://sourceware.cygnus.com - Mingw32 is available at: - ftp://www,mingw.org - - See also http://web.ukonline.co.uk/julian.smart/wxwin/gnuwin32.htm + ftp://www.mingw.org TWIN32 and gcc on Linux -----------------------