Before using the Porting Assistant to
check your files, you need to do the following setup:
- Make your source files accessible to the
Porting Assistant.
- Designate the source files that you intend
to port.
- Provide the Porting Assistant with some
information about your current application.
You must make your source files
accessible prior to starting the Porting Assistant. You can use different approaches
depending on the origin of the sources and the network connections to the Alpha
workstation or server that will run the Porting Assistant.
If your Tru64 UNIX system has network
access to the machine where the sources reside, you might be able to mount the files using
NFS. If that's not possible, you'll need to copy the sources to the Tru64 UNIX system
using a utility such as ftp or tar.
When setting up the sources on the Tru64
UNIX system, consider that the porting process likely will result in changes to the
sources that you might want to reflect in your source file management system (for example,
RCS, SCCS, or DEC/CMS on OpenVMS). The porting process also produces a set of intermediate
files, such as object files.
The remaining setup information is
gathered by the Porting Assistant. As you can see from this screen
shot, you can tell the Porting Assistant which platforms your code currently runs on.
This influences some of the checks that the Porting Assistant will run.
You can designate your source files in
one of two ways:
- Using an existing makefile.
- Specifying the actual source files
(wildcard syntax is valid).
The Porting Assistant gathers the
following information to carry out the checks:
- C, C++ and Fortran source files in your
application.
- Include files.
- #defines and #undefines.
The Porting Assistant needs this
information so it knows which files to analyze and the environment used to build your
initial application.
[Setup] [Locating]
[Understanding] [Making
Changes] |
