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.
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
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.
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 aslo
-travces into the wxWidgets sources.
+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
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
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!
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
projects / wxWidgets.git / blobdiff