TxWin 5.xx and samples, build instructions

- Get the ZIP from: http://www.dfsee.com/download/txwinlib.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)

- Standard build script will use a few other scripts, to be added
to a 'tools' directory (or anywhere in your PATH) manually:

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

  These tools are packaged in the txwtools.zip archive

- 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)
  The macOS versions build directly with 'make' or 'make all'

- 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' and 'sam8' are the most complete samples at the moment.

- The 'txt', 'sam1' and 'sam2' project also contain the needed
  files to build on macOS, but require the Xcode environment
  there, with gcc (or rather the replacements, CLANG+LLDB)
  They build using 'make' in the project base directory,
  and are aimed at source-level debug in the Xcode IDE


Enjoy!

Jan van Wijk
Fsys Software
