steve@robobar.co.uk (Steve Bleazard) (05/24/90)
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
staff@cadlab.sublink.ORG (Alex Martelli) (05/29/90)
And, as we're talking about cross-development: does anybody know of a Fortran compiler that can be used for cross-compilation from a Unix host to an OS/2 target? If you know of any - can its output be linked on the Unix host with other object files, such as those built by a cross C compiler, or extracted from a native OS/2 library; will it support OS/2 dynamic libs; what about debugging, can one use this compiler with Codeviews or the Logitech OS/2 one; etc etc??? Any info on such a cross-development setup would be just dandy, thanks! -- Alex Martelli - CAD.LAB s.p.a., v. Stalingrado 45, Bologna, Italia Email: (work:) staff@cadlab.sublink.org, (home:) alex@am.sublink.org Phone: (work:) ++39 (51) 371099, (home:) ++39 (51) 250434; Fax: ++39 (51) 366964 (work only; any time of day or night).
bill@zycor.uucp (Bill Mahoney) (06/05/90)
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!