Converting From Binder To Nld And Noft; Object File Differences; Table 9-1. Corresponding Binder Tasks And Native Utilities - HP nld Manual

9
Converting From Binder to nld and
noft
The nld and noft utilities replace the Binder product to support the object files
created by the native C, C++, COBOL, and pTAL compilers. nld and noft are used in
the same part of the development process as Binder. You can perform most, but not
all, tasks previously performed by Binder with nld and noft.

Table 9-1. Corresponding Binder Tasks and Native Utilities

Binder Task
Build a loadfile from separate object files
Build and specify a user library
Reduce the size of object files by removing their linking and symbolic
debugging information
Display object file contents
Produce load maps and cross-reference listings
Modify values in the code and data blocks of an object file
Search, replace, or reorder code and data blocks in an object file
nld and noft have different syntax and semantics than Binder. Unlike Binder, nld is
not an interactive tool. It executes a command based on what you specify on the
command line or in a command file.
Subsections:

Object File Differences

Linking Unit Differences
Comparing Binder Commands to nld Options
Comparing Binder Commands to noft Options
For additional information, see the TNS/R Native Application Migration Guide.
Object File Differences
Because of file format differences between a TNS or accelerated object file and a
native object file, nld and noft do not operate on TNS or accelerated object files.
Unlike TNS and accelerated object files, which can be both linkfiles and loadfiles,
native object files are either linkfiles or loadfiles, but not both. For more information on
native object files, see
File Structure.
on page 9-1
on page 9-2
Native Object Files on page 1-2 and
nld and noft Manual—520384-003
9 -1
on page 9-3
on page 9-6
Section 8, Native Object
Native Utility
nld
nld
nld
noft
noft
Not available.
Not available.