TxWindows 1.xx and samples, build instructions

- Use SubVersion to check out the TxWin project to your local disk
  (or get the ZIP from: http://www.dfsee.com/download/txwin1xx.zip)

- Make sure the environment is set correctly using 'setenvtx.cmd'
  This may require updating, or setting other environment variables
  like 'toolkit' and 'watcom' first. (see the 'setenvtx.cmd' file)

  Note: For the current versions of OpenWatcom, the toolkit files
        from the compiler are NOT complete enough to build TxWin!
        You need to use the 'regular' OS2 toolkit from IBM,
        as present with eComStation or by other means.
        Make sure to set the TOOLKIT environment variable!

        I have updated the files for the upcoming OpenWatcom 1.4
        compiler release to include the required definitions ...
        These changes should be present in release-candidate 3

- Standard makefiles will use some external tools that you may have
  to download (Google/Hobbes :-) and add to your tools directory
  (or anywhere in your PATH) manually:

  - tee.exe             ;pipe output to file and screen (OS/2)
  - lxLite.exe          ;executable compressor  (runs on OS/2)
  - upx.exe             ;executable compressor  (runs on DOS)

- Two internal tools used with the projects build scripts are:

  - b.cmd               ;a quick build shortcut, calls buildscript
  - buildsub.cmd        ;the actual build per variant, called
                         by the buildscript, must be in PATH!

- Each subproject (txlib, txt, sam1 ...) comes with a 'build'cmd'
  that will build one or all platform variants using the specific
  makefiles inside the tree, and the 'makefile.mif' in the root
  of that subproject (quick build 'b.cmd' calls these scripts)

- Creating a new project (application) is best done by copying
  one of the sample directories completely (xcopy /s) and
  updating the filenames and makefile accordingly.
  'sam7' is the most complete sample at the moment.


Enjoy!

Jan van Wijk
Fsys Software