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:
@@ -1,45 +1,48 @@
|
||||
<html>
|
||||
|
||||
<HTML>
|
||||
<head>
|
||||
<title>wxWindows 2 FAQ</title>
|
||||
</head>
|
||||
|
||||
<HEAD>
|
||||
<TITLE>wxWindows 2 FAQ</TITLE>
|
||||
</HEAD>
|
||||
<body bgcolor=#ffffff text=#000000 vlink="#00376a" link="#00529c" alink="#313063">
|
||||
|
||||
<BODY BGCOLOR=#FFFFFF TEXT=#000000 VLINK="#00376A" LINK="#00529C" ALINK="#313063">
|
||||
|
||||
<font face="Arial, Lucida Sans, Helvetica">
|
||||
<font face="arial, lucida sans, helvetica">
|
||||
|
||||
<table width=100% border=0 cellpadding=3 cellspacing=0>
|
||||
<tr>
|
||||
<td bgcolor="#004080" align=left height=24 background="images/bluetitlegradient.gif">
|
||||
<font size=+1 face="Arial, Lucida Sans, Helvetica" color="#FFFFFF">
|
||||
<font size=+1 face="arial, lucida sans, helvetica" color="#ffffff">
|
||||
<b>wxWindows 2 FAQ</b>
|
||||
</font>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<P>
|
||||
<p>
|
||||
|
||||
Welcome to the wxWindows FAQ. Please select a category:<P>
|
||||
Welcome to the wxWindows FAQ. Please select a category:<p>
|
||||
|
||||
<ul>
|
||||
<li><a href="faqgen.htm">General questions</a>
|
||||
<li><a href="faqgtk.htm">wxWindows 2 for GTK+</a>
|
||||
<li><a href="faqmsw.htm">wxWindows 2 for Windows</a>
|
||||
<li><a href="faqmot.htm">wxWindows 2 for Motif</a>
|
||||
<li><a href="faqx11.htm">wxWindows 2 for X11</a>
|
||||
<li><a href="faqmac.htm">wxWindows 2 for Mac</a>
|
||||
<li><a href="faqcmn.htm">Questions common to all platforms</a>
|
||||
<li><a href="faqgtk.htm">GTK+ questions</a>
|
||||
<li><a href="faqmsw.htm">MS Windows questions</a>
|
||||
<li><a href="faqmot.htm">Motif questions</a>
|
||||
<li><a href="faqx11.htm">X11 questions</a>
|
||||
<li><a href="faqmac.htm">Mac questions</a>
|
||||
</ul>
|
||||
|
||||
<P>
|
||||
<p>
|
||||
|
||||
For further information, please see the <a href="http://www.wxwindows.org" target=_top>wxWindows Web site</a>,
|
||||
plus install.txt (per port), todo.txt (per port), and bugs.txt (all ports).
|
||||
<P>
|
||||
For further information, please see the
|
||||
<a href="http://www.wxwindows.org" target=_top>wxWindows Web site</a>,
|
||||
<a href="http://mintzer.pqdot.net/cgi-bin/wiki/wiki.pl" target=_top>wxWiki</a>
|
||||
and install.txt (per port), todo.txt (per port), and bugs.txt (all ports) files
|
||||
in your wxWindows installation.
|
||||
<p>
|
||||
|
||||
</font>
|
||||
|
||||
</BODY>
|
||||
</body>
|
||||
|
||||
</HTML>
|
||||
</html>
|
||||
|
@@ -1,3 +1,4 @@
|
||||
|
||||
<HTML>
|
||||
|
||||
<HEAD>
|
||||
@@ -25,15 +26,18 @@ See also <a href="faq.htm">top-level FAQ page</a>.
|
||||
<h3>List of questions in this category</h3>
|
||||
<ul>
|
||||
<li><a href="#whatis">What is wxWindows?</a></li>
|
||||
<li><a href="#licence">Can I use wxWindows 2 for both proprietary projects, and GPL'ed projects?</a></li>
|
||||
<li><a href="#support">Is there support?</a></li>
|
||||
<li><a href="#users">Who uses wxWindows?</a></li>
|
||||
<li><a href="#platforms">What platforms are supported by wxWindows 2?</a></li>
|
||||
<li><a href="#specific">How does wxWindows 2 support platform-specific features?</a></li>
|
||||
<li><a href="#platforms">What platforms are supported by wxWindows?</a></li>
|
||||
<li><a href="#specific">How does wxWindows support platform-specific features?</a></li>
|
||||
<li><a href="#stl">Does wxWindows use STL? or the standard string class?</a></li>
|
||||
<li><a href="#richedit">Is there a rich edit/markup widget for wxWindows 2?</a></ li>
|
||||
<li><a href="#richedit">Is there a rich edit/markup widget for wxWindows?</a></ li>
|
||||
<li><a href="#exceptions">How to use C++ exceptions with wxWindows?</a></ li>
|
||||
<li><a href="#dev">How is wxWindows 2 being developed?</a></li>
|
||||
<li><a href="#distrib">How is wxWindows 2 distributed?</a></li>
|
||||
<li><a href="#dev">How is wxWindows being developed?</a></li>
|
||||
<li><a href="#distrib">How is wxWindows distributed?</a></li>
|
||||
<li><a href="#future">What are the plans for the future?</a></li>
|
||||
<li><a href="#base">What is wxBase?</a></li>
|
||||
<li><a href="#univ">What is wxUniversal?</a></li>
|
||||
<li><a href="#jave">What about Java?</a></li>
|
||||
<li><a href="#help">How can I help the project?</a></li>
|
||||
@@ -54,7 +58,7 @@ You don't have to use C++ to use wxWindows: there is a <a href="http://wxpyt
|
||||
and also a <a href="http://wxperl.sourceforge.net" target=_top>Perl interface</a>.
|
||||
<P>
|
||||
|
||||
<h3>Can I use wxWindows 2 for both proprietary (commercial) projects, and GPL'ed projects?</h3>
|
||||
<h3><a name="licence">Can I use wxWindows 2 for both proprietary (commercial) projects, and GPL'ed projects?</a></h3>
|
||||
|
||||
Yes. Please see the <a href="newlicen.htm">licence</a> for details, but basically
|
||||
you can distribute proprietary binaries without distributing any source code, and neither will wxWindows
|
||||
@@ -64,7 +68,7 @@ The conditions for using wxWindows 2 are the same whether you are a personal, ac
|
||||
or commercial developer.
|
||||
<P>
|
||||
|
||||
<h3>Is there support?</h3>
|
||||
<h3><a name="support">Is there support?</a></h3>
|
||||
|
||||
No official support, but the mailing list is very helpful and some people say that
|
||||
wxWindows support is better than for much commercial software. The developers are
|
||||
@@ -81,6 +85,9 @@ quite large for a list of this type.<P>
|
||||
|
||||
See <a href="users.htm">Users</a> for a list of some users and their applications, and
|
||||
also <A href="feedback.htm">Feedback</a> for comments.<P>
|
||||
Our highest-profile user yet is industry veteran and Lotus Corp. founder Mitch Kapor
|
||||
and his <a href="http://www.osafoundation.org" target=_new>Open Source Applications Foundation</a>.
|
||||
<P>
|
||||
|
||||
<H3><a name="platforms">What platforms are supported by wxWindows 2?</a></H3>
|
||||
|
||||
@@ -159,10 +166,9 @@ or by adding this to a header before you include any STL files:<P>
|
||||
These are the possibilities so far:<P>
|
||||
|
||||
<ul>
|
||||
<li>The richedit sample has a text editor that does markup.
|
||||
<li>See <a href="http://www.scintilla.org" target=_top>www.scintilla.org</a> for
|
||||
a very nice syntax-highlighting editor widget. Robin Dunn is writing a wxWindows wrapper
|
||||
for this widget.
|
||||
a very nice syntax-highlighting editor widget. Robin Dunn has written a wxWindows wrapper
|
||||
for this widget, available in the wxWindows distribution under contrib/src/stc.
|
||||
<li>If you only need to display marked-up information, rather than edit it,
|
||||
then wxHTML will suit your needs. wxHTML is built into wxWindows - please see the reference
|
||||
manual for details, and samples/html.
|
||||
@@ -200,29 +206,29 @@ There are a few issues to keep in mind, though:
|
||||
|
||||
<p>
|
||||
|
||||
<H3><a name="dev">How is wxWindows 2 being developed?</a></H3>
|
||||
<H3><a name="dev">How is wxWindows being developed?</a></H3>
|
||||
|
||||
We are using the <a href="cvs.htm">CVS</a> system to develop and maintain wxWindows. This allows
|
||||
us to make alterations and upload them instantly to the SourceForge server, from
|
||||
us to make alterations and upload them instantly to the server, from
|
||||
which others can update their source.<P>
|
||||
|
||||
To build source from CVS, see the file BuildCVS.txt in the top-level wxWindows distribution
|
||||
directory.<P>
|
||||
|
||||
<H3><a name="distrib">How is wxWindows 2 distributed?</a></H3>
|
||||
<H3><a name="distrib">How is wxWindows distributed?</a></H3>
|
||||
|
||||
By ftp, and via the <a href="cdrom2.htm">wxWindows CD-ROM</a>.
|
||||
<P>
|
||||
If you are feeling adventurous, you may also check out the sources directly
|
||||
from the <a href="cvs.htm">cvs</a>
|
||||
from <a href="cvs.htm">cvs</a>.
|
||||
<p>
|
||||
|
||||
<H3><a name="future">What are the plans for the future?</a></H3>
|
||||
|
||||
Currently we're working too hard on getting wxWindows 2 finished (are GUI toolkits ever
|
||||
Currently we're working too hard on getting wxWindows finished (are GUI toolkits ever
|
||||
finished?) to think very far ahead. However, we know we want to make wxWindows as robust
|
||||
and well-publicised as possible. We also want to aim for better platform-independence of
|
||||
resources such as icons and bitmaps, standardising on the PNG for all platforms.<P>
|
||||
resources such as icons and bitmaps, standardising on PNG and XPM for all platforms.<P>
|
||||
|
||||
Other possibilities include: DCOM/CORBA compatibility; a wxWindows book;
|
||||
<a href="http://wxworkshop.sourceforge.net/">wxWorkshop</a>, an IDE;
|
||||
@@ -234,12 +240,24 @@ their product.<P>
|
||||
The high-level goal of wxWindows is to be thought of as the number one C++ framework,
|
||||
for virtually any platform. Move over, MFC!<P>
|
||||
|
||||
<h3><a name="base">What is wxBase?</a></h3>
|
||||
|
||||
wxBase is a subset of wxWindows comprised by the non-GUI classes. It includes
|
||||
wxWindows container and primitive data type classes (including wxString,
|
||||
wxDateTime and so on) and also useful wrappers for the operating system objects
|
||||
such as files, processes, threads, sockets and so on. With very minor
|
||||
exceptions wxBase may be used in exactly the same way as wxWindows but it
|
||||
doesn't require a GUI to run and so is ideal for creating console mode
|
||||
utilities or server programs. It is also possible to create a program which can
|
||||
be compiled either as a console application (using wxBase) or a GUI one (using
|
||||
a full featured wxWindows port).
|
||||
|
||||
<H3><a name="univ">What is wxUniversal?</a></H3>
|
||||
|
||||
wxUniversal is a new port of wxWindows being currently actively developed. The
|
||||
main difference is that wxUniversal implements all controls (or widgets) in
|
||||
wxWindows itself thus allowing to have much more flexibility (i.e. support for
|
||||
themes even under MS Windows!). It also means that it is now much easier to
|
||||
The main difference between wxUniversal-based ports (such as wxX11, wxMGL) and other ports (such as wxMSW, wxGTK+, wxMac)
|
||||
is that wxUniversal implements all controls (or widgets) in
|
||||
wxWindows itself thus allowing to have much more flexibility (for example, support for
|
||||
themes even under MS Windows). It also means that it is now much easier to
|
||||
port wxWindows to a new platform as only the low-level classes must be ported
|
||||
which make for a small part of the library.
|
||||
<p>
|
||||
@@ -255,7 +273,7 @@ from Java, and the level of interest in wxWindows is as high as ever.<P>
|
||||
|
||||
Please check out the <a href="http://www.wxwindows.org/develop2.htm">Community</a> pages,
|
||||
in particular the <a href="projects.htm">suggested projects</a>, and
|
||||
mail <a href="mailto:julian.smart@btopenworld.com">Julian Smart</a> or the developers' mailing list with your own suggestions.<P>
|
||||
mail the developers' mailing list with your own suggestions.<P>
|
||||
|
||||
</font>
|
||||
|
||||
|
@@ -1,3 +1,4 @@
|
||||
|
||||
<HTML>
|
||||
|
||||
<HEAD>
|
||||
@@ -25,12 +26,13 @@ See also <a href="faq.htm">top-level FAQ page</a>.
|
||||
<h3>List of questions in this category</h3>
|
||||
|
||||
<ul>
|
||||
<li><a href="#wxgtk">What is wxWindows 2 for GTK?</a></li>
|
||||
<li><a href="#wxgtk">What is wxWindows 2 for GTK+?</a></li>
|
||||
<li><a href="#locale">Why doesn't reading floating point numbers work when using wxWindows?</a></li>
|
||||
<li><a href="#gnome">Does wxGTK have GNOME support?</a></li>
|
||||
<li><a href="#redhat">Warning about GTK libraries supplied with RedHat</a></li>
|
||||
<li><a href="#wxgtk">What is wxWindows 2 for GTK?</a></li>
|
||||
<li><a href="#bincompat">What range of Intel Linux platforms will a given application binary be usable on?</a></li>
|
||||
<li><a href="#static">Can I statically link the GTK+ library?</a></li>
|
||||
<li><a href="#charinframe">Why does my simple program using <tt>EVT_CHAR</tt> doesn't work?</a></li>
|
||||
</ul>
|
||||
|
||||
<hr>
|
||||
@@ -69,9 +71,9 @@ so may be added without dependence on libraries. Other features may be supported
|
||||
future, probably as a separate library.
|
||||
<P>
|
||||
|
||||
<h3><a name="redhat">Warning about GTK libraries supplied with RedHat</a></h3>
|
||||
<h3><a name="redhat">Warning about GTK+ libraries supplied with RedHat</a></h3>
|
||||
|
||||
It seems that some versions of RedHat include a badly patched version of GTK (not wxGTK)
|
||||
It seems that some versions of RedHat include a badly patched version of GTK+ (not wxGTK)
|
||||
which causes some trouble with wxWindows' socket code. Common symptoms are that when
|
||||
a client tries to establish a connection to an existing server which refuses the request,
|
||||
the client will get notified twice, first getting a LOST event and then a CONNECT event.
|
||||
@@ -89,6 +91,23 @@ and programs linked against it will not run with version
|
||||
on a 2.1.X system. It will then run on practically all
|
||||
Linux distros (if you link you app statically against
|
||||
the image libraries and std C++ lib)."
|
||||
<P>
|
||||
|
||||
<h3><a name="#static">Can I statically link the GTK+ library?</a></h3>
|
||||
|
||||
No, this is not possible. It leads to crashes in GTK+.
|
||||
<P>
|
||||
|
||||
<h3><a name="#charinframe">Why does my simple program using
|
||||
<tt>EVT_CHAR</tt> doesn't work?</a></h3>
|
||||
|
||||
In wxGTK, the frames never get focus and so can never receive <tt>CHAR</tt>
|
||||
nor <tt>KEY</tt> events so an <tt>EVT_CHAR</tt> handler for a frame will be
|
||||
never called. To receive these events, you should create a <tt>wxPanel</tt>
|
||||
inside the frame and register the key event handlers for the panel, not the
|
||||
frame.
|
||||
|
||||
<p>
|
||||
|
||||
</font>
|
||||
|
||||
|
@@ -1,3 +1,4 @@
|
||||
|
||||
<HTML>
|
||||
|
||||
<HEAD>
|
||||
@@ -201,7 +202,8 @@ Statically-linked wxWindows 2 programs are smaller than wxWindows 1.xx programs,
|
||||
wxWindows 2 has been designed to reduce dependencies between classes, and other
|
||||
techniques. The linker will not include code from the library that is not (directly or
|
||||
indirectly) referenced
|
||||
by your application. So for example, the 'minimal' sample is less than 300KB using VC++ 6.<P>
|
||||
by your application. So for example, the 'minimal' sample is less than 500KB using VC++ 6
|
||||
(note that this figure may be greater for the latest version of wxWindows).<P>
|
||||
|
||||
If you want to distribute really small executables, you can
|
||||
use <a href="http://www.un4seen.com/petite/" target=_top>Petite</a>
|
||||
@@ -210,6 +212,12 @@ will shrink to a mere 250KB. With this sort of size, there is reduced incentive
|
||||
use DLLs. Another good compression tool is <a href="http://upx.sourceforge.net/" target=_top>UPX</a>.
|
||||
<P>
|
||||
|
||||
Please do not be surprised if MinGW produces a statically-linked minimal executable of 1 MB. Firstly, gcc
|
||||
produces larger executables than some compilers. Secondly, this figure will
|
||||
include most of the overhead of wxWindows, so as your application becomes more
|
||||
complex, the overhead becomes proportionaly less significant. And thirdly, trading executable compactness
|
||||
for the enormous increase in productivity you get with wxWindows is almost always well worth it.
|
||||
|
||||
<H3><a name="mfc">Is wxWindows compatible with MFC?</a></H3>
|
||||
|
||||
There is a sample which demonstrates MFC and wxWindows code co-existing in the same
|
||||
@@ -392,7 +400,11 @@ VZ
|
||||
|
||||
This can happen if you have a child window intercepting EVT_CHAR events and swallowing
|
||||
all keyboard input. You should ensure that event.Skip() is called for all input that
|
||||
isn'used by the event handler.
|
||||
isn'used by the event handler.<P>
|
||||
|
||||
It can also happen if you append the submenu to the parent
|
||||
menu {\it before} you have added your menu items. Do the append {\it after} adding
|
||||
your items, or accelerators may not be registered properly.<P>
|
||||
|
||||
<H3><a name="#regconfig">Why can I not write to the HKLM part of the registry with wxRegConfig?</a></H3>
|
||||
|
||||
@@ -414,7 +426,7 @@ First, you can use wxRegKey directly, for example:
|
||||
regKey.SetName(idName);
|
||||
|
||||
{
|
||||
wxLogNull dummy;
|
||||
wxLogNull dummy;
|
||||
if (!regKey.Create())
|
||||
{
|
||||
idName = wxT("HKEY_CURRENT_USER\\SOFTWARE\\My Company\\My Product\\Stuff\\");
|
||||
|
@@ -124,6 +124,13 @@ translations as of wxWindows 2.3.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td valign=center>Greek</td>
|
||||
<td align=center valign=center><IMG SRC="images/no.gif" ALT="Done"></td>
|
||||
<td align=center valign=center><A HREF="mailto:tsolako1@otenet.gr">Tsolakos Stavros</A>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td valign=center>Hungarian</td>
|
||||
<td align=center valign=center><IMG SRC="images/yes.gif" ALT="Done"></td>
|
||||
@@ -131,6 +138,14 @@ translations as of wxWindows 2.3.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td valign=center>Indonesian</td>
|
||||
<td align=center valign=center><IMG SRC="images/yes.gif" ALT="Done"></td>
|
||||
<td align=center valign=center>
|
||||
<a href="mailto:bambang@3wsi.com">Bambang Purnomosidi D. P.</a>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td valign=center>Italian</td>
|
||||
<td align=center valign=center><IMG SRC="images/yes.gif" ALT="Done"></td>
|
||||
@@ -157,6 +172,7 @@ translations as of wxWindows 2.3.
|
||||
<td align=center valign=center><IMG SRC="images/yes.gif" ALT="Ok"></td>
|
||||
<td align=center valign=center><A HREF="mailto:rolinsky@mema.ucl.ac.be">Roman Rolinsky</A>,
|
||||
<A HREF="mailto:vadim@wxwindows.org">Vadim Zeitlin</A>
|
||||
<A HREF="mailto:kai@cmail.ru">Andrew V. Samoilov</A>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
@@ -179,6 +195,13 @@ translations as of wxWindows 2.3.
|
||||
<A HREF="mailto:kgb@compart.fi">Kaj G Backas</A></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td valign=center>Turkish</td>
|
||||
<td align=center valign=center><IMG SRC="images/yes.gif" ALT="Ok"></td>
|
||||
<td align=center valign=center><A HREF="mailto:dogusanh@dynaset.org">Hakki Dogusan</A></td>
|
||||
</tr>
|
||||
|
||||
|
||||
</table>
|
||||
|
||||
<br>
|
||||
@@ -196,15 +219,14 @@ translations. Here are the the steps you should follow:
|
||||
<ol>
|
||||
<li>Get the latest version of the file <tt>locale/wxstd.po</tt> from the
|
||||
wxWindows source tree: if you're using <a href="cvs.htm">cvs</a>
|
||||
or the <a href="http://wxwindows.sf.net/snapshots/">daily
|
||||
snapshots</a>, you should already have it. Otherwise you can always
|
||||
or the <a href="http://wxwindows.sf.net/snapshots/">daily snapshots</a>,
|
||||
you should already have it. Otherwise you can always
|
||||
retrieve it directly from the cvs repository via the Web interface
|
||||
<a href="http://cvs.wxwindows.org/cgi-bin/viewcvs.cgi/wxWindows/locale/wxstd.po">
|
||||
here</a>.
|
||||
<a href="http://cvs.wxwindows.org/viewcvs.cgi/wxWindows/locale/wxstd.po">here</a>.
|
||||
|
||||
<li>Rename it to <tt>XY.po</tt> where <tt>"XY"</tt> is the 2 letter
|
||||
<a href="http://www.iso.ch/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html">
|
||||
ISO country code</a> for your language.
|
||||
<a href="http://lcweb.loc.gov/standards/iso639-2/englangn.html">ISO 639-1 language code</a>
|
||||
for your language.
|
||||
|
||||
<li>Translate the strings in this file using either your favourite text
|
||||
editor or a specialized tool such as Vaclav Slavik's excellent
|
||||
|
@@ -1,6 +1,6 @@
|
||||
<html>
|
||||
<head>
|
||||
<title>Platforms supported by wxWindows 2.x</title>
|
||||
<title>Platforms supported by wxWindows 2.4</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
|
||||
<meta name="Author" content="Vadim Zeitlin">
|
||||
</head>
|
||||
@@ -20,10 +20,11 @@
|
||||
|
||||
</p>
|
||||
|
||||
You will find below the list of all supported platforms for different ports of wxWindows 2.x (wxMSW/wxGTK/wxMotif ports
|
||||
only). The cross icon in the third column doesn't mean that the platform is not supported, but just that wxWindows hasn't
|
||||
been tested on it recently (the table is being updated for wxWindows 2.3.3
|
||||
currently).
|
||||
You will find below the list of all supported platforms for different ports of
|
||||
wxWindows 2.x (wxMSW/wxGTK/wxMotif ports only). The cross icon in the third
|
||||
column doesn't mean that the platform is not supported, but just that
|
||||
wxWindows hasn't been tested on it recently (the table is being updated for
|
||||
wxWindows 2.4.0 currently).
|
||||
<p>
|
||||
See also:
|
||||
|
||||
@@ -86,9 +87,20 @@ often don't work.
|
||||
<tr> <td>wxMotif with gcc 2.95</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td><br></td><td>with <a href="http://www.openmotif.org">OpenMotif</a></td>
|
||||
</tr>
|
||||
|
||||
<tr> <td bgcolor="#fafafa"><br></td><td bgcolor="#fafafa" colspan=5> All BSD systems tests are for wxGTK using gcc. </td>
|
||||
<tr>
|
||||
<td bgcolor="#F0F0F0" align=center valign=center rowspan=1>FreeBSD</td>
|
||||
<td>wxGTK with gcc</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>VZ</td><td>Limited thread support on older systems</td>
|
||||
<td>version from 3.2 to 4.6, x86</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>VZ</td><td><br></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td bgcolor="#FFFFFF" align=center valign=center rowspan=1>NetBSD</td>
|
||||
<td>1.6, Alpha</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>VZ</td><td><br></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td bgcolor="#F0F0F0" align=center valign=center rowspan=1>OpenBSD</td>
|
||||
<td>3.1, Alpha</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>VZ</td><td>Some problems with shared libraries, ok with static ones</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
|
Reference in New Issue
Block a user