Files
harbour-core/harbour/contrib/hbtpathy
Przemyslaw Czerpak 4057472258 2009-07-11 15:38 UTC+0200 Przemyslaw Czerpak (druzus/at/priv.onet.pl)
* harbour/config/os2/watcom.cf
  * harbour/config/os2/dir.cf
  * harbour/config/os2/install.cf
    * small cleanup for builds with *nix like shells and cross builds

  * harbour/contrib/rddads/Makefile
    ! disabld from OS2 builds - if ADS supports OS2 then please speak-up

  * harbour/include/hbthread.h
    * added small hack as workaround for missing OS2 declarations

  * harbour/source/rtl/filesys.c
    ! fixed typo in OS2 builds

  * harbour/source/rtl/hbproces.c
    ! fixed non GCC OS2 builds

  * harbour/contrib/hbtpathy/tpos2.c
    ! fixed casting in OS2 builds

  * harbour/contrib/xhb/hbserv.c
    ! disabled from OS2 non GCC builds

   Now I can create OS2 OpenWatcom build in my Linux box using this simple
   script:

      #!/bin/sh
      if [ -z "${WATCOM}" ]; then
         export WATCOM="/opt/lng/watcom"
         export INCLUDE="${WATCOM}/h:${WATCOM}/h/os2"
         export PATH="${WATCOM}/binl:$PATH"
      fi

      export HB_ARCHITECTURE=os2
      export HB_COMPILER=watcom
      export HB_INSTALL_PREFIX="$(pwd)/hb-os2/watcom"

      #cross build settings
      # this should be fixed and we should use HB_PPGEN_PATH as direct
      # reference to hbpp binaries and HB_COMP_PATH as direct reference
      # to harbour binaries in all builds. Otherwise we have to create
      # some hacks to create platform specific names for above binaries
      # i.e. in *nixes links with .exe extension.
      export HB_PPGEN_PATH="/tmp/cros-hb"
      export HB_BIN_COMPILE="/tmp/cros-hb"

      export HB_USER_PRGFLAGS="${HB_USER_PRGFLAGS} -D__PLATFORM__OS2"
      export HB_USER_PRGFLAGS="${HB_USER_PRGFLAGS} -undef:__PLATFORM__UNIX"
      export HB_USER_PRGFLAGS="${HB_USER_PRGFLAGS} -undef:__PLATFORM__LINUX"
      # eliminate libraries which scans for local host header files
      export HB_XBUILD=yes

      ./make_gnu.sh "$@"

   It should work also in Windows with MSys.
   This should resolve the problem with testing OS2 builds, at least
   for OpenWatcom. I do not know if GCC for OS2 is available as cross
   build environment.
   I think that Viktor can quite easy adopt hbmk2 for OS2 cross compilation.
2009-07-11 13:39:02 +00:00
..

/*
 * $Id$
 */

Telepathy is the best serial communication library for Nantucket/CA-Cl*pper.
I ported a significant amount of the functionality contained in Telepathy in
this Flagship port.

The .prg (in the MyTelepathy.tar package) is meant to be compiled with
Flagship and provide some of the functionality of the Telepathy serial
library from Extrasensory Inc.  I've talked to Ira Emus, the proprietor of
Extrasensory and he's ok with what I've done here.  But Extrasensory has no
involvement or responsibility with this project.

I wrote this originally on RedHat Linux 5.1 and I've tested it on RedHat
6.2.  And now Neolinux 2.0.1 and 2.1.  I've tested it on kernels 2.0.x - 2.4.x.
Your mileage may vary.

I only ported the parts of Telepathy that I needed.  If you need other parts
of the telepathy libarary, Use the Source... (and send me your new functions)

I tried to keep parameter counts and orders as consistent as possible between
this Telepathy and the real Telepathy.  The only difference I can think of is
the parameter list for tp_open (and tp_reopen).  That's just because unix has
filename comports like /dev/ttyS0 and dos has com port numbers like 1.  I kept
the com port number thing so that all the telepathy functions (and all your
code) that uses com port number won't need to be changed.  But you do need to
change the calls to tp_open.

Feel free to use, modify, distribute, hack, kludge, append, extend or whatever
you like to this source code.  You can (at your own risk) compile it into any
program you wish and sell or freely distribute the resulting application.  I
would prefer you make your application Free and distribute the source.  But who
am I to say - the suite of applications that my company sells that I originally
wrote this for is closed source.

Though I use this code in a production environment for a suite of programs that
my company actually sells, I make no promises (expressed or implied) about its
stability, functionality, effectiveness or anything else.  I warn you now
that if you use my code, you're doing so at your own risk and it will probably
blow up your computer.  But that's a risk you'll just have to take.

There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE (thanks RMS).
This software is totally as is, you may use it at your own risk.

This is freeware.  But if you actually use this in your program, please send
me email at dan@boba-fett.net.  I'd just be curious to see if anyone ever
uses it.

If you find a bug or write some new code for this project, pretty please send
me email with it.

- Dan Levitt <dan@boba-fett.net>