Xref: utzoo comp.unix.xenix:11784 comp.unix.i386:5417
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!mcsun!ukc!slxsys!ibmpcug!robobar!steve
From: steve@robobar.co.uk (Steve Bleazard)
Newsgroups: comp.unix.xenix,comp.unix.i386
Subject: Re: Xenix to Dos cross-development
Keywords: Xenix Dos cross-development linking
Message-ID: <1990May24.072813.8466@robobar.co.uk>
Date: 24 May 90 07:28:13 GMT
References: <77@rsoft.bc.ca>
Organization: Robobar Ltd., Perivale, Middx., ENGLAND.
Lines: 41

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.
>
>One short question:  Is it possible to make use of third party libraries
>intended for MSC version 5.1 ?
>
>I am attempting to use the CWORTHY screen/form management library in a dos
>application I am developing under SCO 386 Xenix.  Everything compiles fine
>but the linker chokes on the first library - "Invalid object module".  Does
>this mean I haven't used the appropriate flags to cc or does this mean I am
>out of luck?

  1) SCO Xenix object files targeted for the 80286 are compatible with
     DOS object files.

  2) Object files for the 386 _may_ be compatible with some dos extender
     linkers

  3) DOS Libraries are _not_ compatible with SCO Xenix libraries.

To use a third party library with SCO Xenix use the following procedure

  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)

Steve
-- 
Steve.Bleazard@RoboBar.Co.Uk        | Phone:  +44 81 991 1142 x153
Snr Software Engineer, Robobar Ltd. | Fax:    +44 81 998 8343 (G3)
22 Wadsworth Road, Perivale.        |
Middx., UB6 7JD ENGLAND.            | ...!ukc!robobar!steve