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
The Development Environment
Open System Services Porting Guide—520573-006
2-5
Compilation Options for C and C++ Programs
environments. For TNS/R and TNS/E systems, it is the version of the c89 utility and C
run-time code that determine whether the program runs as a TNS or a native process.
See C and C++ Compilation Using the c89 Utility on page 2-10 for details on the
TNS/R native and TNS C compilation tools.
You can use the TNS C compilation tools in the following environments:
•
D30 and later TNS environment (OSS and Guardian)
Table 2-1. Cross-Compilation Options for Generating OSS and Guardian
Executable Files
Compiler
Available
on PC
c89 Flag to
Generate OSS
Executable File
c89 Flag to Generate
Guardian Executable
File
Executable File
(And Where It
Runs)
Vendor C Yes N.A. N.A. Workstation
ETK with cross-
compilers
Yes N.A. (Select target
of OSS)
N.A. (Select target of
Guardian)
Native D40 and
later (TNS/R
target); native
H-series (TNS/E
target)
Native c89 in
OSS, D40 and
later, H-series
Yes Yes, default -Wsystype=guardian Native D40 and
later; native H-
series
NMC in Guardian,
D40 and later; G-
series, H-series
N.A. -Wsystype=oss Yes, default Native D40 and
later; native G-
series
NMCPLUS in
Guardian, D40 and
later, G-series, H-
series
N.A. -Wsystype=oss Yes, default Native D40 and
later; native G-
series
CCOMP in
Guardian, H-series
N.A. -Wsystype=oss Yes, default Native H-series
CPPCOMP in
Guardian, H-series
N.A. -Wsystype=oss Yes, default Native H-series
TNS c89 in OSS,
D40
N.A. Yes, default -Wsystype=guardian TNS D40 and
later; TNS G-
series
c89 in OSS, D30 N.A. Yes, default -Wsystype=guardian TNS D30 and
later
c89 in Guardian,
D30
N.A. -Wsystype=oss Yes, default TNS D30 and
later; TNS G-
series
c89 in Guardian,
H-series
Yes -Wsystype=oss Yes, default H-series