Open System Services Porting Guide (G06.24+, H06.03+)
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 Introduction to Porting
- 2 The Development Environment
- 3 Useful Porting Tools
- 4 Interoperating Between User Environments
- Purpose of Interoperability
- The OSS User Environment
- OSS Commands for the Guardian User
- Guardian Commands for the UNIX User
- OSS Pathname and Guardian Filename Conversions
- Running the OSS Shell and Commands From TACL
- Running Guardian Commands From the OSS Shell
- Running OSS Processes With Guardian Attributes
- Using OSS Commands to Manage Guardian Objects
- 5 Interoperating Between Programming Environments
- 6 OSS Porting Considerations
- 7 Porting UNIX Applications to the OSS Environment
- 8 Migrating Guardian Applications to the OSS Environment
- General Migration Guidelines
- C Compiler Issues for Guardian Programs
- Using New and Extended Guardian Procedures
- Using OSS Functions in a Guardian Program
- Interoperating With OSS Programs
- Starting an OSS Program From the Guardian Environment
- C Compiler Considerations for OSS Programs
- Porting a Guardian Program to the OSS Environment
- How Arguments Are Passed to the C or C++ Program
- Differences in the Two Run-Time Environments
- Which Run-Time Routines Are Available
- Use of Common Run-Time Environment (CRE) Functions
- Replacing Guardian Procedure Calls With Equivalent OSS Functions
- Which IPC Mechanisms Can Be Used
- Interactions Between Guardian and OSS Functions
- 9 Porting From Specific UNIX Systems
- 10 Native Migration Overview
- 11 Porting or Migrating Sockets Applications
- 12 Porting Threaded Applications
- A Equivalent OSS and UNIX Commands for Guardian Users
- B Equivalent Guardian Commands for OSS and UNIX Users
- C Equivalent Inspect Debugging Commands for dbx Commands
- D Equivalent Native Inspect Debugging Commands for dbx Commands
- E Standard POSIX Threads Functions: Differences Between the Previous and Current Standards
- Glossary
- Index
Porting From Specific UNIX Systems
Open System Services Porting Guide—520573-006
9-4
Development Tools
•
cflow produces a chart of external references for checking program
dependencies.
•
ctrace prints out variables during execution for following execution of a C
program, one statement at a time.
•
cxref analyzes a group of C source files and builds a cross-reference table for
symbols in each for checking program dependencies.
•
indent indents and formats C source files to produce more readable C code.
•
unifdef resolves and removes from preprocessor output code lines bound with
the #ifdef directive.
You should perform your source code analysis before porting to the OSS environment.
Therefore, these tools are not provided with the OSS environment. Note that #ifdef
directives can be very useful in ported programs when source code is used to compile
object code for more than one platform.
Object File Utilities
The following object file utilities might be available on your UNIX workstation:
•
ar is an archive utility for maintaining object modules. It helps to build a set of
routines in a library file from which you can add or delete modules. More
information about using ar is available in the ar(1) online reference page; ar is
also available in the OSS environment.
If you manage your object files on the workstation using ar, then you can manage
the corresponding object files in the OSS environment using ar.
•
lorder generates an ordered listing of object files. More information about using
lorder is available in the lorder(1) online reference page; lorder is not
available in the OSS environment.
If you track your object files on the workstation using lorder, then you will know
which object files you must replace after porting your application to the OSS
environment.
•
nm prints a symbol table of an object file. More information about using nm is
available in the nm(1) online reference page; nm is also available in the OSS
environment.
If you manage your symbols on the workstation using nm, then you can manage
your symbols in the OSS environment using nm.
•
size reports the number of bytes in an object’s sections of loadable segments.
This information can help you adjust the memory management portion of your
application when porting to the OSS environment. More information about using
size is available in the size(1) online reference page; size is not available in
the OSS environment.