| | 1 | |
| | 2 | <HTML> |
| | 3 | |
| | 4 | <HEAD> |
| | 5 | <TITLE>wxWindows 2 for GTK FAQ</TITLE> |
| | 6 | </HEAD> |
| | 7 | |
| | 8 | <BODY BGCOLOR=#FFFFFF TEXT=#000000 VLINK="#00376A" LINK="#00529C" ALINK="#313063"> |
| | 9 | |
| | 10 | <font face="Arial, Lucida Sans, Helvetica"> |
| | 11 | |
| | 12 | <table width=100% border=0 cellpadding=3 cellspacing=0> |
| | 13 | <tr> |
| | 14 | <td bgcolor="#004080" align=left height=24 background="images/bluetitlegradient.gif"> |
| | 15 | <font size=+1 face="Arial, Lucida Sans, Helvetica" color="#FFFFFF"> |
| | 16 | <b>wxWindows 2 for GTK FAQ</b> |
| | 17 | </font> |
| | 18 | </td> |
| | 19 | </tr> |
| | 20 | </table> |
| | 21 | |
| | 22 | <P> |
| | 23 | |
| | 24 | See also <a href="faq.htm">top-level FAQ page</a>. |
| | 25 | <hr> |
| | 26 | <h3>List of questions in this category</h3> |
| | 27 | <li><a href="#wxgtk">What is wxWindows 2 for GTK?</a></li> |
| | 28 | <li><a href="#gnome">Does wxGTK have GNOME support?</a></li> |
| | 29 | <li><a href="#redhat">Warning about GTK libraries supplied with RedHat</a></li> |
| | 30 | <li><a href="#wxgtk">What is wxWindows 2 for GTK?</a></li> |
| | 31 | <li><a href="#bincompat">What range of Intel Linux platforms will a given application binary be usable on?</li> |
| | 32 | |
| | 33 | <hr> |
| | 34 | |
| | 35 | wxWindows 2 for GTK is a port of wxWindows to the <a href="http://www.gimp.org/gtk" target=_top>GTK+ toolkit</a>, |
| | 36 | which is freely available for most flavours of Unix with X. wxWindows 2 for GTK is |
| | 37 | often abbreviated to wxGTK. wxGTK has a separate home page <a href="http://www.freiburg.linux.de/~wxxt" target=_top>here</a>. |
| | 38 | <P> |
| | 39 | |
| | 40 | <h3><a name="gnome">Does wxGTK have GNOME support?</a></h3> |
| | 41 | |
| | 42 | Currently wxGTK does not have any features that would involve dependence on any desktop |
| | 43 | environment's libraries, so it can work on GNOME, KDE and with other window managers |
| | 44 | without installation hassles. Some GNOME and KDE integration features are file based, and |
| | 45 | so may be added without dependence on libraries. Other features may be supported in the |
| | 46 | future, probably as a separate library. |
| | 47 | <P> |
| | 48 | |
| | 49 | <h3><a name="redhat">Warning about GTK libraries supplied with RedHat</a></h3> |
| | 50 | |
| | 51 | It seems that some versions of RedHat include a badly patched version of GTK (not wxGTK) |
| | 52 | which causes some trouble with wxWindows' socket code. Common symptoms are that when |
| | 53 | a client tries to establish a connection to an existing server which refuses the request, |
| | 54 | the client will get notified twice, first getting a LOST event and then a CONNECT event. |
| | 55 | This problem can be solved by updating GTK with an official distribution of the library. |
| | 56 | <P> |
| | 57 | |
| | 58 | <h3><a name="bincompat">What range of Intel Linux platforms will a given application binary be usable on?</h3> |
| | 59 | |
| | 60 | Robert Roebling replies:<P> |
| | 61 | |
| | 62 | "The important thing is the libc version that your app |
| | 63 | is linked against. The most recent version is 2.2.5 |
| | 64 | and programs linked against it will not run with version |
| | 65 | 2.1.X so that you will fare best if you compile your app |
| | 66 | on a 2.1.X system. It will then run on practically all |
| | 67 | Linux distros (if you link you app statically against |
| | 68 | the image libraries and std C++ lib)." |
| | 69 | |
| | 70 | </font> |
| | 71 | |
| | 72 | </BODY> |
| | 73 | |
| | 74 | </HTML> |
projects / wxWidgets.git / blame_incremental