Index of /tcl/ftparchive/sorted/net/win

      Name                   Last modified     Size  Description

[DIR] Parent Directory 29-Jan-99 12:29 - [   ] README 23-Oct-96 06:08 4k

This is the directory where you compile and install the Windows NT
versions of the scotty extension for Tcl/Tk and the tkined network
editor. This directory also contains source files specific to Windows
NT. 

Note, this Windows port is still very early alpha code. This is
ongoing work and not yet complete. Use at your own risk. Do not send
bug reports unless you have a patch for it. In a similar way, do not
ask for enhancements unless you work on it yourself and send us a
patch once the enhancement is up and running.


1. Introduction
---------------

This is the directory where you configure and compile the Windows
version of the Tnm Tcl extension. This directory also contains source
files for Tnm that are specific to Microsoft Windows. The rest of
this file contains information specific to the Windows version of Tcl.


2. Distribution notes
---------------------

The Windows port of the Tnm extension is distributed as part of the
common source release. It contains makefiles which assume that you
have installed the Tcl/Tk binary release available from Sun
Microsystems in the default place. You need to make some adjustments
in case you have installed Tcl/Tk somewhere else. The Tnm extension
will be compiled into a dynamic loadable library (dll). No main scotty
program is compiled since there is no support for a complete event
driven Tcl interpreter on the Windows platform in the current Tcl/Tk
release.


3. Compiling Scotty
-------------------

In order to compile Scotty for Windows, you need the following items:

	Tcl 7.5 Binary Distribution (plus any patches)

	Borland C++ 4.52/5.0 (both 16-bit and 32-bit compilers)
	  or
	Visual C++ 2.x/4.x

In the "win" subdirectory of the source release, you will find two
files called "makefile.bc" and "makefile.vc".  These are the makefiles
for the Borland and Visual C++ compilers respectively.  You should
copy the appropriate one to "makefile" and update the paths at the
top of the file to reflect your system configuration.  Now you can use
"make" (or "nmake" for VC++) to build the dynamic link libraries.

Note, if you are using Visual C++ together with the Tcl/Tk release
from Sun Microsystems, you will also need the vclibs41.zip" file
available from the ftp.sunlabs.com:/pub/tcl archive. This file
contains the .lib import files needed to link against the binary
release of Tcl 7.5. Unzip the vclibs41.zip archive into the current
directory to create the tcl75.lib and tk41.lib files.

You also need to install the oncrpc.lib file derived from the ONC RPC
port to Windows NT done by Martin F. Gergeleit and the resolv.lib file
derived from the bind-4.9.4 port to NT. These files are available from
ftp.ibr.cs.tu-bs.de in /pub/local/tkined/Win32 for the Borland C++
compiler (bclibs21.zip) and the Visual C++ compiler (vclibs21.zip).
More information about the oncrpc port to NT can be found at:

	http://set.gmd.de/RS/Mitarbeiter/gergeleit/oncrpc.html

Information about the bind resolver and the port to Windows NT
can be found at:

	http://www.vix.com/isc/bind.html

Note that your have to hack the sources a bit in order to compile the
oncrpc.lib and resolv.lib archives needed for the Tnm port.


4. Open Tnm portability problems
--------------------------------

1. The snmp command crashes in the snmp test suite.

2. The snmp command does not allow to receive traps by more than one
   application.

3. The following commands have not yet been ported: icmp.


5. Open Tkined portability problems
-----------------------------------

1. I had to add a dummy function to tkiStripchart.c and tkiBarchart.c
   to make the Borland compiler/linker happy. There must be a better
   solution.

2. Tkineds file dialog crashes my NT machines. What a nice operating
   system, isn't it?

3. Tkined relies on a three button mouse so moving objects does not
   work on NT (with a two button mouse).

4. Tkined fails to load bitmaps for additional icons.

5. I did not see an interpreter starting up yet - probably some more
   work required here.


6. Acknowledgements:
--------------------

The Windows NT porting project has been sponsored by Optical Data
Systems (http://www.ods.com).