+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, @@ -76,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: @@ -117,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. @@ -128,7 +130,7 @@ article.
-
@@ -168,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 +See also the wxWiki Contents for more information.
@@ -320,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). @@ -491,13 +497,13 @@ bool myGlobalConfig::Write (const wxString& key, const wxString& value)Is MS Active Accessibility supported?
-This is being worked on. Please see this page +This is being worked on. Please see this page for the current status.-
Why does Visual C++ complain about corrupted project files{/a>
+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 @@ -510,6 +516,59 @@ Of course, another possibility is to always use only the Windows cvs client and to avoid this problem completely.+
Visual C++ gives errors about multiply defined symbols, what can I do?
+ +If you get errors like this + ++MSVCRTD.lib(MSVCRTD.dll) : error LNK2005: _xxxxxx already defined in LIBCD.lib(yyyyy.obj) ++ +when linking your project, this means that you used different versions of CRT +(C Run-Time) library for wxWindows (or possibly another library) and the main +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 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 +CRT which is a good choice but may be problematic when distributing your +applications if you don't include the CRT DLL in your installation -- in this +case you may decide to switch to using a static CRT version. If you build with +wxUSE_THREADS == 0 you may also use the non MT-safe version as it is +slightly smaller and faster. +
+But the most important thing is to use the same CRT setting for +all components of your project. + +
Why do I get compilation errors when using wxWidgets with DirectShow?
+ +If you get errors when including Microsoft DirectShow or DirectDraw headers, +the following message from Peter Whaite could help: ++> This causes compilation errors within DirectShow: +> +> wxutil.h(125) : error C2065: 'EXECUTE_ASSERT' : undeclared identifier +> amfilter.h(1099) : error C2065: 'ASSERT' : undeclared identifier + +The reason for this is that __WXDEBUG__ is also used by the DXSDK (9.0 +in my case) to '#pragma once' the contents of +DXSDK/Samples/C++/DirectShow/BaseClasses/wxdebug.h. So if __WXDEBUG__ +is defined, then wxdebug.h doesn't get included, and the assert macros +don't get defined. You have to #undef __WXDEBUG__ before including the +directshow baseclass's <streams.h>. ++ + +How do I handle Windows messages in my wxWidgets program?
+ +To handle a Windows message you need to override a virtual +MSWWindowProc() method in a wxWindow-derived class. You should then +test if nMsg parameter is the message you need to process and perform +the necessary action if it is or call the base class method otherwise. + +