Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!ucdavis!iris!foss
From: foss@iris.ucdavis.edu (Jim Alves-Foss)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Separate overlay files w/ MSC
Message-ID: <5484@ucdavis.ucdavis.edu>
Date: 3 Oct 89 16:57:08 GMT
References: <8000057@m.cs.uiuc.edu>
Sender: uucp@ucdavis.ucdavis.edu
Reply-To: foss@iris.ucdavis.edu (Jim Alves-Foss)
Organization: U.C. Davis - Department of Electrical Engineering and Computer Science
Lines: 19

In article <8000057@m.cs.uiuc.edu> wright@m.cs.uiuc.edu writes:
>
>
> ... I would
>like to be able to store overlays in separate file(s), but MSC by
                                                            ^^^
>itself seems unwilling.  Can someone tell me how other programs
>are developed with separate files for overlays?
>
This is your problem. MSC can compile separate source files quite 
easily - thus creating separate object files. 

NOW to combine those object files and libraries you need a LINKER
(ah there's the problem). MS LINK does not allow you to create separate
overlay files. I have heard of other linkers (PLINK (?)) that let 
you do this. Anyone out there know of these linkers?

-Jim Alves-Foss (foss@iris.ucdavis.edu)  /* Of course these are MY opinions */
                (foss@127.120.57.20)     /* and may change without warning. */