X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/b55a176b25afb2f838601b260aea28912fcd83a5..27bb2b7cea271d91e272452ff361f948e38dc539:/docs/gtk/install.txt diff --git a/docs/gtk/install.txt b/docs/gtk/install.txt index 168a270a2b..2999a2995e 100644 --- a/docs/gtk/install.txt +++ b/docs/gtk/install.txt @@ -1,4 +1,4 @@ -wxWindows 2.3 for GTK installation +wxWindows 2.4 for GTK installation ---------------------------------- IMPORTANT NOTE: @@ -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.4.0, gcc 2.95.4, Redhat 6.2 * The simplest case ------------------- @@ -41,6 +41,30 @@ If you want to remove wxWindows on Unix you can do this: > ldconfig > exit +* The GTK+ 2 case +----------------- + +wxGTK 2.4.0 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 +recent version of GTK+ 2.0, do this + +> ./configure --with-gtk --enable-gtk2 --enable-unicode +> make +> su +> make install +> ldconfig +> exit + +If you are adventurous, you can install the FcConfig 2.0 package +and the Pango library from CVS (or a very recent snapshot from +the upcoming 1.2 series) and set do "export GDK_USE_XFT=1" so +that the display as well as the printing code will use render +using the same FreeType code even for Far Eastern encodings. + +Expect problems. + * The expert case ----------------- @@ -49,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. @@ -70,7 +94,7 @@ cd .. md buildgtkd cd buildgtkd -../configure --with-gtk --enable-debug_flag +../configure --with-gtk --enable-debug make cd .. @@ -317,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 -----------------