If you are new to wxWindows then you shoud go to original wxWindows www, find how to use CVS and subscribe  to wxos2 list.

Or you can simply go to Hobbes, take  cvs1107.zip   and all work with anonymous access is as simple as possible:

• Create directory, say J:\wx2
• copy to that directory CVS.exe or place it somewhere at PATH
• create empty file .cvspass
• create cmd like that

SET CVSROOT=:pserver:anonymous@cvs.wxWindows.sourceforge.net:/cvsroot/wxwindows
set HOME=J:\wxx2
REM only for first time connect, Simply press Enter on password question
REM CVS -d:pserver:anonymous@cvs.wxWindows.sourceforge.net:/cvsroot/wxwindows login
CVS -z3 -d:pserver:anonymous@cvs.wxWindows.sourceforge.net:/cvsroot/wxwindows checkout wxOS2
 
 

• I  use VAC3 from comand line to compile sources.. as pure lib without DLL yet. It produce  huge exe file and relatively long linking time, but it is more convenient for debugging with  VAC debugger
• Next I use VAC3 WorkWrame to debug minimal  application  with automatically building of  project.  I copy all files I want  to /samples/minimal directory and debug and change it while all other stuff includes via libs. But there is one problem. MakeMake  falls with original recurcive includes, so I comment all foreing stuff  (with "change" ) such as #include "wx/msw/blabla.h", next I comment all  "#include "wx/wxprec.h",  so if you see that it is wrong - then uncomment it
• Some my comments are marked as EK
• my own wxWindows\include\wx\os2\SETUP.H - changed  to minimal state, and  include features with our progress (default setup.h includes all features)
• I use TCPV40HDRS  and wxUSE_CONSOLEDEBUG  macros in my os2\SETUP.H
• some debug printf macros are placed to some .h and .cpp, also a number of prinf's is placed  across sources commented and uncommented  - so that it is possible  for those debug printfs infiltrate to  CVS sources