Galaxy Communicator Documentation:
Upgrading from 3.2 to 3.3
Upgrading to Galaxy Communicator 3.3 is
simple. There are only two upgrades, and the first affects only a small
number of users.
This document describes only the steps
required or recommended to upgrade existing features of Galaxy Communicator.
You can find a list of new features here.
You can find the complete release notes here.
Step
1: Updating cross-compilation support
The new cross-compilation
support requires any users of this facility to change their approach
completely. Previously, the value of the GC_CROSS
environment variable was a directory which contained files which allowed
the user to describe the system architecture and operating system of the
target platform. This information is now contained directly in a single
/bin/sh
file which is the value of GC_CROSS.
Because this functionality was previously experimental, we will not provide
step-by-step upgrade instructions; see the documentation
for a detailed example.
Step
2: Upgrading to the Open Source Toolkit
If you are using any of the servers in contrib/MITRE/servers,
be advised that they have been removed from the distribution in order to
form the initial basis of the Open Source Toolkit, available from http://communicator.sourceforge.net.
Step
3: Upgrading flags which set Java Hub client behavior
The connection policy flags for Java Hub clients
has been updated to coincide with support in the other language bindings.
See the Java
notes for details.
Please send comments and suggestions to:
bugs-darpacomm@linus.mitre.org
Last updated January 9, 2002.
Copyright (c) 2001 - 2002
The MITRE
Corporation
ALL RIGHTS RESERVED