Running The Nld Utility In The Oss Environment; Example; Creating A Loadfile (Oss); Creating A User Library (Oss) - HP nld Manual

nld Utility
Running the nld Utility in the OSS
Environment
To run the nld utility in the OSS environment, use the following syntax:
option
nld [
option
is an nld option (a flag and its parameters, if any). A flag begins with a hyphen (-).
You must include a space between a flag and its parameters except after the -l
and -L flags. Case is not significant when specifying nld options, except for the
-l and -L flags. For descriptions of nld flags and their parameters, see
nld Options.
Filename
is an OSS filename for a TNS/R native object file. The nld utility supports /E OSS
directories. Depending on the flags specified, the object file can be a linkfile or a
loadfile.
You can specify input from the command line or use the option
page 3-6, which allows the contents of a file to be entered in the command input at the
point specified. Use the -obey option to supply several options or input filenames.

Example 2-3

combines object files named objecta, objectb, and objectc and
creates a loadfile named objectd.
Example 2-3. Creating a Loadfile (OSS)
nld objecta objectb objectc -o objectd
Example 2-4 links the object files named obj1.o and obj2.o together into a user
library named lib.
Example 2-4. Creating a User Library (OSS)
nld obj1.o obj2.o -ul -o lib
Example 2-5 links object files named obj3.o and obj4.o together into a program
named prog. It also associates prog with a user library with the Guardian name
$a.b.c. The backslash prevents the shell from misinterpreting the dollar sign ($).
Example 2-5. Creating a Program File (OSS)
nld obj3.o obj4.o -o prog -libname \$a.b.c
] ... Filename
nld and noft Manual—520384-003
2 -3

Running the nld Utility in the OSS Environment

-fl or -obey
Section 3,
on