Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!labrea!decwrl!hplabs!hp-sdd!ucsdhub!jack!man!crash!jeh
From: jeh@crash.CTS.COM (Jamie Hanrahan)
Newsgroups: comp.os.vms
Subject: Re: linking against RTLs
Message-ID: <1466@crash.CTS.COM>
Date: Mon, 3-Aug-87 14:10:29 EDT
Article-I.D.: crash.1466
Posted: Mon Aug  3 14:10:29 1987
Date-Received: Tue, 4-Aug-87 06:30:07 EDT
References: <12322163796.34.AWALKER@RED.RUTGERS.EDU> <3027@blia.BLI.COM>
Reply-To: jeh@crash.CTS.COM (Jamie Hanrahan)
Distribution: world
Organization: Crash TS, El Cajon, CA
Lines: 10
Keywords: linking object compatibility
Summary: You can ship the objects


Another poster mentioned the /nosysshr option to the linker and its 
limitations.  If you can't live with the limitations, one useful workaround
is to ship the object files and link them on the target machine.  DEC does
this for many of their layered products; in fact, one of the example 
product installation command procedures in the "Developer's Guide to 
VMSINSTAL" illustrates this, though it isn't specifically mentioned in 
the text.  The handiest trick is to put all the objects into one or a
few object libraries and use /include to pull out the main program
mo.St.St.