-Installing wxWidgets 2.8.0
+Installing wxWidgets for Windows
-----------------------------------------------------------
-This is wxWidgets 2.8.0 for Microsoft Windows 9x/ME, Windows NT,
+This is wxWidgets for Microsoft Windows 9x/ME, Windows NT,
Windows 2000, Windows XP and Windows CE.
These installation notes can be found in docs/msw/install.txt
IMPORTANT NOTE: If you experience problems installing, please
re-read this instructions and other related files (changes.txt,
-readme.txt, FAQ) carefully before mailing wx-users. Preferably,
-try to fix the problem first and then upload a patch to
-SourceForge:
+readme.txt, FAQ) carefully before posting to wx-users list.
- http://sourceforge.net/patch/?group_id=9863
+If you are sure that you found a bug, please report it at
+wxWidgets Trac:
-Please report bugs using the SourceForge bug tracker:
+ http://trac.wxwidgets.org/newticket
+
+Please notice that often trying to correct the bug yourself is the
+quickest way to fix it. Even if you fail to do it, you may
+discover valuable information allowing us to fix it while doing
+it. We also give much higher priority to bug reports with patches
+fixing the problems so this ensures that your report will be
+addressed sooner.
- http://sourceforge.net/bugs/?group_id=9863
Unarchiving
============================================================
-A setup program is provided (setup.exe) to automatically copy
+A setup program is provided (wxMSW-x.x.x-setup.exe) to automatically copy
files to a directory on your hard disk. Do not install into a
path that contains spaces.
- All common, generic and MSW-specific wxWidgets source;
- samples and demos;
- documentation in MS HTML Help format;
-- makefiles for most Windows compilers, plus CodeWarrior,
- BC++ and VC++ IDE files;
-- JPEG library source;
-- TIFF library source;
-- Object Graphics Library, Tex2RTF, wxSTC, etc.
+- makefiles for most Windows compilers, plus CodeWarrior
+ and VC++ IDE files;
+- JPEG, TIFF, PNG, ZLIB, wxSTC, REGEX, EXPAT library sources.
Alternatively, you may unarchive the .zip form by hand:
wxMSW-x.y.z.zip where x.y.z is the version number.
General installation notes
==========================
-If installing from the CVS server, copy include/wx/msw/setup0.h to
+If installing from the SVN server, copy include/wx/msw/setup0.h to
include/wx/msw/setup.h and edit the resulting file to choose
the features you would like to compile wxWidgets with[out].
"Configuring the build" below). This is a typical set of release ANSI build
libraries (release versions on left, debug on right side):
- wxbase28.lib wxbase28d.lib
- wxbase28_net.lib wxbase28d_net.lib
- wxbase28_xml.lib wxbase28d_xml.lib
- wxmsw28_core.lib wxmsw28d_core.lib
- wxmsw28_html.lib wxmsw28d_html.lib
- wxmsw28_adv.lib wxmsw28d_adv.lib
+ wxbase29.lib wxbase29d.lib
+ wxbase29_net.lib wxbase29d_net.lib
+ wxbase29_xml.lib wxbase29d_xml.lib
+ wxmsw29_core.lib wxmsw29d_core.lib
+ wxmsw29_html.lib wxmsw29d_html.lib
+ wxmsw29_adv.lib wxmsw29d_adv.lib
Their Unicode debug counterparts in wxUniversal build would be
- wxbase28ud.lib
- wxbase28ud_net.lib
- wxbase28ud_xml.lib (notice these libs are same for wxUniv and wxMSW)
- wxmswuniv28ud_core.lib
- wxmswuniv28ud_html.lib
- wxmswuniv28ud_adv.lib
+ wxbase29ud.lib
+ wxbase29ud_net.lib
+ wxbase29ud_xml.lib (notice these libs are same for wxUniv and wxMSW)
+ wxmswuniv29ud_core.lib
+ wxmswuniv29ud_html.lib
+ wxmswuniv29ud_adv.lib
These directories also contain subdirectory with wx/setup.h header. This
-subdirectory is named after port, Unicode, wxUniv and debug settings and
+subdirectory is named after port, Unicode, wxUniv and debug settings and
you must add it to include paths when compiling your application. Some
examples:
If you want to build DLL configurations in wx.dsw project you unfortunately
need to build them in the proper order (jpeg, png, tiff, zlib, regex, expat,
- base, net, odbc, core, gl, html, media, qa, adv, dbgrid, xrc, aui, richtext)
- manually because VC6 doesn't always respect the correct build order.
+ base, net, odbc, core, gl, html, media, qa, adv, dbgrid, xrc, aui, richtext,
+ propgrid) manually because VC6 doesn't always respect the correct build order.
Alternatively, use the special wx_dll.dsw project which adds the
dependencies to force the correct order (but, because of this, doesn't work
2.4.2), which can be downloaded for free from:
http://www.borland.com/products/downloads/download_cbuilder.html
+We have found that the free Turbo Explorer and commercial BDS work fine; the
+debugger is very good. To avoid linker errors you will need to add
+-DSHARED=1 to the makefile line for the library
+
The version 5.6 included in Borland C++ Builder 2006 works as well after the
following small change: please remove the test for __WINDOWS__ from line 88
of the file BCCDIR\include\stl\_threads.h.
This produces a couple of libraries in the lib\bcc_lib directory.
2. Change directory to a sample or demo such as samples\minimal, and type
- 'make -f makefile.bcc'. This produces a windows exe file - by default
+ 'make -f makefile.bcc'. This produces a windows exe file - by default
in the bcc_mswd subdirectory.
Note (1): the wxWidgets makefiles assume dword structure alignment. Please
Note (3): If you wish debug messages to be sent to the console in
debug mode, edit makefile.bcc and change /aa to /Tpe in link commands.
-Cmpilation succeeds with CBuilderX personal edition and CBuilder6, but
+Using the Debugger and IDE in BDS or Turbo Explorer
+---------------------------------------------------
+
+
+Doubleclick / open samples\minimal\borland.bdsproj. The current version
+is to be used with a dynamic build of wxWidgets-made by running
+make -f Makefile.bcc -DBUILD=debug -DSHARED=1
+in wxWidgets\build\msw. You also need the wxWidgets\lib\bcc_dll
+directory in your PATH. The debugger tracks your source and also
+traces into the wxWidgets sources.
+
+To use this to debug other samples, copy the borland_ide.cpp
+and borland.bdsproj files, then replace all occurences of
+"minimal" with the name of the new project files
+
+Compilation succeeds with CBuilderX personal edition and CBuilder6, but
you may have to copy make.exe from the 5.5 download to the new bin directory.
-Compiling using the IDE files for Borland C++ 5.0 and using CBuilder IDE
-(v1-v6): not supported
+
+Compiling using the IDE files for Borland C++ 5.0 and using CBuilder IDE
+(v1-v6): not supported
+
** REMEMBER **
** The authoritative list of files is in build/bakefiles/files.bkl
1. CodeWarrior Pro 7 project files in XML format are already
- included in wxMSW-2.8.0.zip and the setup version.
+ included in wxMSW-2.8.x.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
+ you are working from the SVN 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
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
+ working from the SVN 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
+ working from the SVN version) to lib\cw7mswd\include\wx\setup.h
5. Import src\wxWidgetsW7.xml to create the project file wxWidgetsW7.mcp.
Store this project file in directory src. You may get warnings about
other environments (such as UNIX or Unix-like, e.g. MSYS where you have
to use configure instead, see the section below)
-Here are the steps required using the provided makefiles:
-
-- If you are using gcc-2.95, edit build\msw\config.gcc and set the GCC_VERSION
- variable to "2.95".
-
-- Use the makefile.gcc files for compiling wxWidgets and samples,
- e.g. to compile a debugging version of wxWidgets:
+Use the makefile.gcc files for compiling wxWidgets and samples,
+e.g. to compile a debugging version of wxWidgets:
> cd c:\wx\build\msw
- > make -f makefile.gcc BUILD=debug
+ > mingw32-make -f makefile.gcc BUILD=debug
> cd c:\wx\samples\minimal
- > make -f makefile.gcc BUILD=debug
+ > mingw32-make -f makefile.gcc BUILD=debug
(See below for more options.)
- Ignore the warning about the default entry point.
+Notice that Windows command interpreter (cmd.exe) and mingw32-make must be
+used, using Bash (sh.exe) and make.exe from MSYS will only work when using
+configure-based build procedure described below!
-- Use the 'strip' command to reduce executable/dll size (note that
- stripping an executable/dll will remove debug information!).
+You can also use the 'strip' command to reduce executable/dll size (note that
+stripping an executable/dll will remove debug information!).
All targets have 'clean' targets to allow removal of object files
and other intermediate compiler files.
The DigitalMars compiler is a free succssor to the Symantec compiler
and can be downloaded from http://www.digitalmars.com/
-
+
1. You need to download and unzip in turn (later packages will overwrite
older files)
Digital Mars C/C++ Compiler Version 8.40 or later
----------------------------------------------------------------
BUILD=release
- Builds release version of the library. It differs from default 'debug'
+ Builds release version of the library. It differs from default 'debug'
in lack of appended 'd' in name of library, does not define __WXDEBUG__
- and not include debug information compiled into object files and the
+ and not include debug information compiled into object files and the
executable.
SHARED=1
Build shared libraries (DLLs). By default, DLLs are not built
(SHARED=0).
-UNICODE=1
- To build Unicode versions of the libraries, add UNICODE=1 to make invocation
- (default is UNICODE=0). If you want to be able to use Unicode version on
+UNICODE=0
+ To build ANSI versions of the libraries, add UNICODE=0 to make invocation
+ (default is UNICODE=1). If you want to be able to use Unicode version on
Windows9x, you will need to set MSLU=1 as well.
This option affect name of the library ('u' is appended) and the directory
----------------------------------------------------------------
MONOLITHIC=1
- Starting with version 2.5.1, wxWidgets has the ability to be built as
+ Starting with version 2.5.1, wxWidgets has the ability to be built as
several smaller libraries instead of single big one as used to be the case
in 2.4 and older versions. This is called "multilib build" and is the
default behaviour of makefiles. You can still build single library
you should set wxUSE_GUI to 1 in setup.h.
USE_OPENGL=1
- Build wxmsw28_gl.lib library with OpenGL integration class wxGLCanvas.
+ Build wxmsw29_gl.lib library with OpenGL integration class wxGLCanvas.
You must also modify your setup.h to #define wxUSE_GLCANVAS 1. Note that
OpenGL library is always built as additional library, even in monolithic
build!
Same as DEBUG_FLAG in behaviour, this option affects whether debugging
information is included in the executable or not.
+TARGET_CPU=AMD64|IA64
+ (VC++ only.) Set this variable to build for x86_64 systems. If unset, x86
+ build is performed.
+
VENDOR=<your company name>
Set this to a short string identifying your company if you are planning to
distribute wxWidgets DLLs with your application. Default value is 'custom'.
This string is included as part of DLL name. wxWidgets DLLs contain compiler
name, version information and vendor name in them. For example
- wxmsw280_core_bcc_custom.dll is one of DLLs build using Borland C++ with
+ wxmsw290_core_bcc_custom.dll is one of DLLs build using Borland C++ with
default settings. If you set VENDOR=mycorp, the name will change to
- wxmsw280_core_bcc_mycorp.dll.
+ wxmsw290_core_bcc_mycorp.dll.
CFG=<configuration name>
Sets configuration name so that you can have multiple wxWidgets builds with
different setup.h settings coexisting in same tree. See "Object and library
directories" below for more information.
+COMPILER_PREFIX=<string>
+ If you build with multiple versions of the same compiler, you can put
+ their outputs into directories like "vc6_lib", "vc8_lib" etc. instead of
+ "vc_lib" by setting this variable to e.g. "vc6". This is merely a
+ convenience variable, you can achieve the same effect (but different dir
+ names) with the CFG option.
+
+
Compiler specific options
----------------------------------------------------------------
* MinGW
If you are using gcc-2.95 instead of gcc3, you must set GCC_VERSION to
-2.95. In build\msw\config.gcc, change
+2.95. In build\msw\config.gcc, change
> GCC_VERSION = 3
to
> GCC_VERSION = 2.95
build\msw\bcc_mswunivd SHARED=0, WXUNIV=1, BUILD=debug
build\msw\vc_mswunivd ditto, with Visual C++
-Libraries and DLLs are copied into subdirectory of lib directory with
+Libraries and DLLs are copied into subdirectory of lib directory with
name derived from compiler and static/DLL setting and setup.h into directory
with name that contains other settings:
If you set CFG to something, the value is appended to directory names. E.g.
for CFG=MyBuild, you'll have object files in
-
+
build\msw\bcc_mswMyBuild
build\msw\bcc_mswdllMyBuild
etc.
etc.
By now it is clear what CFG is for: builds with different CFG settings don't
-share any files and they use different setup.h files. This allows you to e.g.
+share any files and they use different setup.h files. This allows you to e.g.
have two static debug builds, one with wxUSE_SOCKETS=0 and one with sockets
enabled (without CFG, both of them would be put into same directory and there
would be conflicts between the files).
projects / wxWidgets.git / blobdiff