-Installing wxWindows 2.3
-------------------------
+Installing wxWindows 2.3.3
+--------------------------
-This is wxWindows 2.3 for Microsoft Windows 9x/ME, Windows NT,
+This is wxWindows 2.3.3 for Microsoft Windows 9x/ME, Windows NT,
Windows 2000 and Windows XP. This is an unstable development release.
Please note that the library naming conventions for VC++
-compilation have changed between 2.3.1 and 2.3.2. This means that
+compilation have changed after 2.3.1. This means that
you will need to change your application project files. See the
relevant section below for details.
You MUST use the 'cleanall' target (with FINAL=1 or FINAL=0)
before making a different configuration, because otherwise
object files used to build the previous configuration may be
- used accidentally for the current configuation. You might see
+ used accidentally for the current configuration. You might see
this manifested in unexpected link errors or warnings. This problem
doesn't occur when using project files to build wxWindows.
+ To build Unicode versions of the libraries, add UNICODE=1
+ to the nmake invocation ( default is UNICODE=0 ).
+
Note that the wxWindows core library allows you to have debug
and release libraries available simultaneously, by compiling the
objects in different subdirectories, whereas samples must be
set WXWIN=c:\wxwindows
to your autoexec.bat file], and that it uses the FAT (short
name) form with no spaces.
- Make sure your BCCDIR variable is set [e.g add
- set BCCDIR=c:\progra~1\borland\bcc
- to your autoexec.bat file], and that it points to the root directory of
- your Borland C++ installation, and it uses the FAT (short
- name) form with no spaces.
Reboot if needed for the changes to autoexec.bat to take effect.
-2. Change directory to wx\src\msw. Type 'make -f makefile.b32' to
+2. Change directory to src\msw. Type 'make -f makefile.b32' to
make the wxWindows core library. Ignore the warnings about
'XXX' not found in library.
3. Change directory to a sample or demo such as samples\minimal, and type
Please note that the samples have not been exhaustively tested
with this configuration.
-Note (1): the wxWindows library and (some) samples compile in 16-bit mode
+Note (1): In Borland 4.5 and earleir, using bcc.exe you also need to define BCCDIR
+in the autoexec.bat file; like this:
+ set BCCDIR=c:\progra~1\borland\bcc
+ so that it points to the root directory of
+ your Borland C++ installation, and it uses the FAT (short
+ name) form with no spaces.
+
+
+Note (2): 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.
-Note (2): unfortunately most samples won't link in 16-bit mode,
+Note (3): unfortunately most samples won't link in 16-bit mode,
because the automatic data segment exceeds 64K. The minimal
sample links and runs, however.
-Note (3): the wxWindows makefiles assume byte structure alignment. Please
+Note (4): the wxWindows makefiles assume byte structure alignment. Please
make sure that your own project or makefile settings use the
same alignment, or you could experience mysterious crashes. To
change the alignment, add a suitable option to the $(CFG) target code
in src/msw/makefile.b32.
-Note (4): if you get undefined _SQL... symbols at link time,
+Note (5): if you get undefined _SQL... symbols at link time,
either install odbc32.lib from the BC++ CD-ROM into your BC++ lib
directory, or set wxUSE_ODBC to 0 in include\wx\msw\setup.h and
recompile wxWindows. The same applies if compiling using the IDE.
-Note (5): BC++ 4.5 (not 5.0) trips up over jdmerge.c in the JPEG folder;
+Note (6): BC++ 4.5 (not 5.0) trips up over jdmerge.c in the JPEG folder;
you will therefore need to set wxUSE_LIBJPEG to 0 in setup.h and remove
the jpeg target from src\msw\makefile.b32, and remove jpeg from
src\makeprog.b32.
-Note (6): [obsolete]
Note (7): If you wish debug messages to be sent to the console in
debug mode, edit src\makeb32.env and change /aa to /Tpe in
Metrowerks CodeWarrior compilation
----------------------------------
-1. Downloaded and unzip wxWindows-x.y.z-cw.zip.
-2. Load the make_cw.mcp project in wx\src, and compile.
-3. Load the make_cw.mcp project in wx\samples\minimal, and compile.
- Further project files for samples will be available in due
- course.
+1. CodeWarrior Pro7 project files in XML format are already
+ included in wxMSW-x.y.z.zip and the setup version.
+2. Review the file include\wx\msw\setup.h (or include\wx\msw\setup0.h if
+ you are working from the CVS version) to make sure the settings reflect
+ what you want. If you aren't sure, leave it alone and go with the
+ default settings. A few notes:
+ - Don't use wxUSE_DEBUG_NEW_ALWAYS: it doesn't mix well with MSL
+ - wxUSE_GLOBAL_MEMORY_OPERATORS works, but memory leak reports
+ will be rather confusing due to interactions with the MSL ANSI
+ and runtime libs.
+3. The project file to build the Win32 wxWindows libraries relies on the
+ Batch File Runner plug-in. This plug-in is not installed as part of
+ a normal CW7 installation. However, you can find this plug-in on the
+ CodeWarrior Reference CD, in the Thrill Seekers folder; it's call the
+ "Batch File Post Linker".
+4. If you choose not to install the Batch File Runner plug-in, then you
+ need to do the following by hand:
+ (1) Create the directories lib\cw7msw\include\wx and copy the file
+ include\wx\msw\setup.h (or include\wx\msw\setup0.h if you are
+ working from the CVS version) to lib\cw7msw\include\wx\setup.h
+ (2) Create the directories lib\cw7mswd\include\wx and copy the file
+ include\wx\msw\setup.h (or include\wx\msw\setup0.h if you are
+ working from the CVS version) to lib\cw7mswd\include\wx\setup.h
+5. Import srcwxWindows.xml to create the project file wxWindows.mcp.
+ Store this project file in directory src. You may get warnings about
+ not being able to find certain project paths; ignore these warnings, the
+ appropriate paths will be created during the build by the Batch File Runner.
+6. Choose the wxlib Win32 debug or wxlib Win32 Release target and build. You
+ will get some warnings about hidden virtual functions, illegal conversions
+ from const pointers to pointers, etc., all of which you can safely ignore.
+ ***Note: if you get errors that the compiler can't find "wx/setup.h", just
+ stop the build and build again. These errors occur because sometimes the
+ compiler starts doing its thing before the copying of setup.h has completed.
+7. The following libraries will be produced depending on chosen
+ target:
+ - wx_x86.lib ANSI Release (static)
+ - wx_x86_d.lib ANSI Debug (static)
+8. Sorry, I haven't had time yet to create and test unicode or DLL versions.
+ Volunteers for this are welcome (as neither DLLs nor unicode builds are
+ big priorities for me ;).
+9. CodeWarrior Pro7 project files (in XML format) are also provided for some
+ of the samples. In particular, for the minimal, controls, dialogs, dnd,
+ and docview samples. You can use these project files as templates for
+ the other samples and for your own projects.
-Note (1): you need CodeWarrior Pro 4 plus the patches to 4.1 from the
-Metrowerks Web site.
-
-Note (2): unfortunately these files are not yet up-to-date for the
-current release.
Symantec C++ compilation
------------------------
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!
+Step (2). 16-bit compilation is left as an exercise for the user!
Salford C++ compilation
-----------------------
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.
+Both Cygwin and MinGW can be used with the same makefiles.
+
+NOTE: some notes specific to old Cygwin ( < 1.1.x )
+ and MinGW ( < 1.0 ) are at the end of this section
+ ( see OLD VERSIONS )
Here are the steps required:
-- Retrieve and install the latest beta of Cygwin, or Mingw32, as per the
+- Retrieve and install the latest version of Cygwin, or Mingw32, as per the
instructions with either of these packages.
- If using Mingw32, you need some extra files to use the wxWindows
These should be extracted to the Mingw32 directory. If you have
already 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
- must hand-patch with Mingw32-gcc295.patches (located in the
- top-level of the wxWindows 2 installation). Mingw32 2.95.2
- and above contain the fixes already.
-
-- Modify the file wx/src/cygnus.bat (or mingw32.bat or mingegcs.bat)
- to set up appropriate variables, if necessary mounting drives.
- 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
- 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 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
backslashes.
- Use the makefile.g95 files for compiling wxWindows and samples,
- e.g.:
+ e.g. to compile a debugging version of wxWindows:
> cd c:\wx\src\msw
> make -f makefile.g95
> cd c:\wx\samples\minimal
> make -f makefile.g95
+ to compile with optimizations:
+ > cd c:\wx\src\msw
+ > make -f makefile.g95 FINAL=1
+ > cd c:\wx\samples\minimal
+ > make -f makefile.g95 FINAL=1
+
+ to compile a DLL:
+ > cd c:\wx\src\msw
+ > make -f makefile.g95 WXMAKINGDLL=1
+ > cd c:\wx\samples\minimal
+ > make -f makefile.g95 WXUSINGDLL=1
+
+ to compile the Unicode version:
+ > cd c:\wx\src\msw
+ > make -f makefile.g95 UNICODE=1
+ > cd c:\wx\samples\minimal
+ > make -f makefile.g95 UNICODE=1
+
+ Options can be combined ( e.g.: UNICODE=1 FINAL=1 )
+
Ignore the warning about the default entry point.
- Use the 'strip' command to reduce executable size.
- 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.
-
-- If using GnuWin32 b18, you will need to copy windres.exe
- from e.g. the Mingw32 distribution, to a directory in your path.
+ flagged when the program quits. You can use Cygwin gdb
+ to debug MinGW executables.
All targets have 'clean' targets to allow removal of object files
-and other intermediate compiler files.
+and other intermediate compiler files and 'cleanall' targets to
+allow removal of all object files and library files.
Notes:
and similarly for glu[32].def.
+OLD VERSIONS:
+
+- If using Mingw32 2.95 and below with wxWindows 2.1 or above, you
+ must hand-patch with Mingw32-gcc295.patches (located in the
+ top-level of the wxWindows 2 installation). Mingw32 2.95.2
+ and above contain the fixes already.
+
+- Modify the file wx/src/cygnus.bat (or mingw32.bat or mingegcs.bat)
+ to set up appropriate variables, if necessary mounting drives.
+ 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
+ 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 Cygwin 1.x releases) or 0
+ (if you have Cygwin betas). If using Mingw32, also set the
+ MINGW32VERSION variable appropriately.
+
+- If using GnuWin32 b18, you will need to copy windres.exe
+ from e.g. the Mingw32 distribution, to a directory in your path.
+
References:
- The Cygwin site is at
- http://sourceware.cygnus.com
+ http://sources.redhat.com/cygwin
- Mingw32 is available at:
ftp://www.mingw.org
projects / wxWidgets.git / blobdiff