This commit was manufactured by cvs2svn to create tag 'wxPy_2_3_4_1'.
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/tags/wxPy_2_3_4_1@18324 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
@@ -11,7 +11,7 @@ IMPORTANT NOTE:
|
||||
|
||||
When sending bug reports tell us what version of wxWindows you are
|
||||
using (including the beta) and what compiler on what system. One
|
||||
example: wxGTK 2.3.3, gcc 2.95.4, Redhat 6.2
|
||||
example: wxGTK 2.3.4, gcc 2.95.4, Redhat 6.2
|
||||
|
||||
* The simplest case
|
||||
-------------------
|
||||
@@ -44,7 +44,7 @@ If you want to remove wxWindows on Unix you can do this:
|
||||
* The GTK+ 2 case
|
||||
-----------------
|
||||
|
||||
wxGTK 2.3.3 has support for the new version 2.0.X of GTK+. This means
|
||||
wxGTK 2.3.4 has support for the new version 2.0.X of GTK+. This means
|
||||
that wxGTK apps can now make use Unicode as the underlying encoding
|
||||
for all text operations. This is a very fundamental change and will
|
||||
need time to stabilize, so be careful. Anyways, after installing a
|
||||
@@ -73,7 +73,7 @@ such as for GTK and Motif, you can now build two complete libraries and use
|
||||
them concurrently. For this end, you have to create a directory for each build
|
||||
of wxWindows - you may also want to create different versions of wxWindows
|
||||
and test them concurrently. Most typically, this would be a version configured
|
||||
with --enable-debug_flag and one without. Note, that only one build can
|
||||
with --enable-debug and one without. Note, that only one build can
|
||||
currently be installed, so you'd have to use local version of the library for
|
||||
that purpose.
|
||||
|
||||
@@ -94,7 +94,7 @@ cd ..
|
||||
|
||||
md buildgtkd
|
||||
cd buildgtkd
|
||||
../configure --with-gtk --enable-debug_flag
|
||||
../configure --with-gtk --enable-debug
|
||||
make
|
||||
cd ..
|
||||
|
||||
@@ -341,6 +341,12 @@ The following options handle the kind of library you want to build.
|
||||
must be compiled with the same debug
|
||||
options.
|
||||
|
||||
--enable-debug Same as --enable-debug_info and
|
||||
--enable-debug_flag together. Unless you have
|
||||
some very specific needs, you should use this
|
||||
option instead of --enable-debug_info/flag ones
|
||||
separately.
|
||||
|
||||
* Feature Options
|
||||
-----------------
|
||||
|
||||
|
Reference in New Issue
Block a user