Remove (Open)Watcom support.

This compiler is not being developed since several years and almost certainly
can't be used to build the current wxWidgets sources anyhow, so remove all
support for it, including a lot of extremely ugly workarounds for its bugs
with template functions.

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@76546 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775

docs/base/readme.txt

@@ -68,20 +68,7 @@ c) Borland
    Please refer to the docs/msw/install.txt. The console sample compiles and
    runs but does not pass all tests.
 
-d) Watcom
-
-   The compilation has been tested only with OpenWatcom but should also work
-   with Watcom 11.0 but probably not the earlier versions.
-
-   To build wxBase itself (only static library build is supported), enter the
-   directory src\msw and type "wmake -f makebase.wat". See also Watcom notes in
-   docs/msw/install.txt.
-
-   There is makefile.wat in samples\console which can be used to build the
-   console sample with Watcom and also shows how can you write your own
-   makefiles for wxBase and Watcom compiler.
-
-e) Other compilers
+d) Other compilers
 
    Unfortunately we don't have the makefiles for any other compilers yet.
 Please contact us if you would like to help us with creating one for the

docs/doxygen/mainpages/const_cpp.h

@@ -167,7 +167,8 @@ compiler used.
                     for compiler version being precisely 7.}
 @itemdef{__XLC__, AIX compiler}
 @itemdef{__WATCOMC__, Watcom C++. The value of this macro corresponds to
-                    the compiler version, @c 1100 is @c 11.0 and @c 1200 is OpenWatcom.}
+                    the compiler version, @c 1100 is @c 11.0 and @c 1200 is OpenWatcom
+                    (not used any more).}
 @endDefList
 
 

docs/doxygen/mainpages/devtips.h

@@ -44,7 +44,7 @@ The file @c "wx/wxprec.h" includes @c "wx/wx.h". Although this incantation may
 seem quirky, it is in fact the end result of a lot of experimentation, and
 several Windows compilers to use precompilation which is largely automatic for
 compilers with necessary support. Currently it is used for Visual C++
-(including embedded Visual C++), Borland C++, Open Watcom C++, Digital Mars C++
+(including embedded Visual C++), Borland C++, Digital Mars C++
 and newer versions of GCC. Some compilers might need extra work from the
 application developer to set the build environment up as necessary for the
 support.
@@ -111,9 +111,9 @@ and this must not be changed.
 On Microsoft Windows, wxWidgets has a different set of makefiles for each
 compiler, because each compiler's @c 'make' tool is slightly different. Popular
 Windows compilers that we cater for, and the corresponding makefile extensions,
-include: Microsoft Visual C++ (.vc), Borland C++ (.bcc), OpenWatcom C++ (.wat)
-and MinGW/Cygwin (.gcc). Makefiles are provided for the wxWidgets library
-itself, samples, demos, and utilities.
+include: Microsoft Visual C++ (.vc), Borland C++ (.bcc) and MinGW/Cygwin
+(.gcc). Makefiles are provided for the wxWidgets library itself, samples,
+demos, and utilities.
 
 On Linux, Mac and OS/2, you use the @c 'configure' command to generate the
 necessary makefiles. You should also use this method when building with

docs/doxygen/mainpages/platdetails.h

@@ -135,8 +135,8 @@ distribution.
 wxMSW is a port of wxWidgets for the Windows platforms (Windows XP and later
 are supported). wxMSW provides native look and feel for each Windows version.
 This port can be compiled with several compilers including Microsoft Studio
-VC++ 2003 or later, Borland 5.5, MinGW32, Cygwin and Watcom as well as
-cross-compilation with a Linux-hosted MinGW32 tool chain.
+VC++ 2003 or later, Borland 5.5, MinGW32, Cygwin as well as cross-compilation
+with a Linux-hosted MinGW32 tool chain.
 
 For further information, please see the files in docs/msw in the distribution.
 

docs/tech/tn0009.htm

@@ -33,7 +33,7 @@ into the executable.<P>
 You can decide to use only XPMs on Windows and Unix, or you could use XPMs on Unix and
 Windows icons under Windows -- the latter will require some #ifdefs in your code or use of the wxICON macro.<P>
 
-If you are using a compiler such as Borland C++, Visual C++ or Watcom C++, you
+If you are using a compiler such as Borland C++ or Visual C++ you
 can use the provided icon editor. However, if using Cygwin or Mingw32, there
 is no icon editor so you must obtain one separately, such as <a href="http://hotfiles.zdnet.com/cgi-bin/texis/swlib/hotfiles/info.html?fcode=00165P">IconEdit32</a>.<P>