+wxWidgets can be used to develop and deliver applications on Windows 95, Windows 98, Windows NT, +Windows 2000, Windows XP, and Windows Vista. A Windows CE +port is also available (see below).
-wxWidgets 2 is designed to make use of WIN32 features and controls. However, unlike Microsoft, -we have not forgotten users of 16-bit Windows. Most features -work under Windows 3.1, including wxTreeCtrl and wxListCtrl using the generic implementation. -However, don't expect very Windows-95-specific classes to work, such as wxTaskBarIcon. The wxRegConfig -class doesn't work either because the Windows 3.1 registry is very simplistic. Check out the 16-bit -makefiles to see what other files have been left out. -
-16-bit compilation is supported under Visual C++ 1.5, and Borland BC++ 4 to 5. +16-bit compilation is only supported for wxWidgets 2.4 and previous versions, +using Visual C++ 1.5 and Borland BC++ 4 to 5.
-wxWidgets 2 for Windows will also compile on Unix with gcc using Wine from WineHQ. +wxWidgets for Windows will also compile on Unix with gcc using Wine from WineHQ. The resulting executables are Unix binaries that work with the Wine Windows API emulator.
-You can also compile wxWidgets 2 for Windows on Unix with Cygwin or Mingw32, resulting +You can also compile wxWidgets for Windows on Unix with Cygwin or Mingw32, resulting in executables that will run on Windows. So in theory you could write your applications using wxGTK or wxMotif, then check/debug your wxWidgets for Windows programs with Wine, and finally produce an ix86 Windows executable using Cygwin/Mingw32, @@ -78,10 +73,19 @@ without ever needing a copy of Microsoft Windows. See the Technical Note on the
+This port supports Pocket PC 2002/2003 and MS Smartphone 2002/2003, using +Embedded Visual C++ 3 or 4. For further information, see the wxMSW section in +the wxWidgets Reference Manual, and also the wxEmbedded page.
+ +For versions of wxWidgets below 2.5, you need to provide the manifest +explicitly, as follows.
+ In the same directory as you have your executable (e.g. foo.exe) you put a file called foo.exe.manifest in which you have something like the following: @@ -119,10 +123,6 @@ line:
1 24 "winxp.manifest" -In wxWidgets 2.5, this will be in the wx/msw/wx.rc and -so will happen automatically so long as you include wx.rc -in your own .rc file.
- For an explanation of this syntax, please see this article. @@ -130,7 +130,7 @@ article.
-
@@ -170,7 +170,8 @@ Watcom C++ is a little slow and the debugger is not really up to today's sta Among the free compilers the best choice seem to be Borland C++ command line tools and mingw32 (port of gcc to Win32). Both of them are supported by -wxWidgets. +wxWidgets. However BC++ has trouble compiling large executables statically, +so you need to dynamically link the wxWidgets libraries.
-
-lib/mswd
+lib/vc_lib/mswd
-or if building the static Release library, lib/msw.
+or if building the static Release library, lib/vc_lib/msw.
See also the wxWiki Contents for more information.
@@ -322,10 +323,13 @@ Code' (and no others). This will then work.
+ +For 2.4.x, there is a system written by Vadim Zeitlin that generates the makefiles from templates using tmake.
-Here are Vadim's notes:
+Here are Vadim's notes on tmake:
To use these new makefiles, you don't need anything (but see below). @@ -359,7 +363,7 @@ The templates are described in tmake ref manual (1-2 pages of text) and are quite simple. They do contain some Perl code, but my Perl is primitive (very C like) so it should be possible for anybody to make trivial modifications to it (I hope that only trivial modifications -will be needed). I've tagged the old makefiles as MAKEFILES_WITHOUT_TMAKE +will be needed). I've tagged the ol makefiles as MAKEFILES_WITHOUT_TMAKE in the cvs, so you can always retrieve them and compare the new ones, this will make it easier to solve the problems you might have.@@ -437,7 +441,7 @@ your items, or accelerators may not be registered properly.
Currently this is not possible because the wxConfig family of classes is supposed to deal with per-user application configuration data, and HKLM is -only supposed to be writable by a user with Administrator privileges. In theory, +only supposed to be writeable by a user with Administrator privileges. In theory, only installers should write to HKLM. This is still a point debated by the wxWidgets developers. There are at least two ways to work around it if you really need to write to HKLM.
@@ -453,7 +457,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\\"); @@ -499,7 +503,7 @@ for the current status.
-
Why does Visual C++ complain about corrupted project files??
+Why does Visual C++ complain about corrupted project files?
If you have downloaded the wxWidgets sources from the cvs using a Unix cvs client or downloaded a daily snapshot in .tar.gz format, it is likely @@ -525,7 +529,7 @@ when linking your project, this means that you used different versions of CRT project. Visual C++ provides static or dynamic and multithread safe or not versions of CRT for each of debug and release builds, for a total of 8 libraries. You can choose among them by going to the "Code generation" -page/subitem of the "C++" tab/item in the project properties dialog in VC6/7. +page/subitem of the "C++" tab/item in the project proprieties dialog in VC6/7.To avoid problems, you must use the same one for all components of your project. wxWindows uses multithread safe DLL version of the