Xref: utzoo comp.unix.xenix:11930 comp.unix.i386:5654
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!ssbell!mcmi!unocss!zycor!bill
From: bill@zycor.uucp (Bill Mahoney)
Newsgroups: comp.unix.xenix,comp.unix.i386
Subject: Re: Xenix to Dos cross-development
Keywords: Xenix Dos cross-development linking
Message-ID: <1990Jun5.140258.6310@zycor.uucp>
Date: 5 Jun 90 14:02:58 GMT
References: <77@rsoft.bc.ca> <1990May24.072813.8466@robobar.co.uk>
Reply-To: bill@zycor.UUCP (Bill Mahoney)
Organization: zycor, Inc. - Omaha, NE
Lines: 21

In article <1990May24.072813.8466@robobar.co.uk> steve@robobar.co.uk (Steve Bleazard) writes:
>In article <77@rsoft.bc.ca> frank@rsoft.bc.ca (Frank I. Reiter) writes:
>>I am looking for help from anyone who has used SCO's Xenix->Dos cross
>>development facilites.

>  1) extract all the modules from the third party library using the DOS lib
>     command.
>  2) recombine the modules using ar(C) under SCO Xenix
>  3) ranlib the new library
>DISCLAIMER:
>  I haven't tried this procedure so it may be wrong in detail (I don't have a
>  MSC manual to hand so I'm not sure about the module extraction)

Yes, this works fine, I have done it with three or four libraries that
I did not have source for. The compiler's .o files will link in with the
new library w/o problems.

-- 
Bill Mahoney			//STEPLIB  DD DSN=SYS2.LINKLIB,DSP=SHR
bill@zycor.UUCP			//SYSPRINT DD SYSOUT=A
				.... Huh? Wha? Oh! It was only a bad dream!