home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!sdd.hp.com!usc!howland.reston.ans.net!spool.mu.edu!agate!linus!progress!leary
- From: leary@progress.COM (Jim Leary)
- Subject: Re: Microsoft library access from Turbo C?
- Message-ID: <1993Jan22.175232.18997@progress.com>
- Sender: usenet@progress.com (Mr. Usenet)
- Nntp-Posting-Host: misseq
- Organization: Progress Software Corp.
- References: <1993Jan21.171455.215@kenyon.edu>
- Date: Fri, 22 Jan 1993 17:52:32 GMT
- Lines: 32
-
- sullivan@kenyon.edu writes:
-
- >I have some DOS hardware with a software library to use it written for
- >Microsoft C (ver 4.00). Is there a way to link code I write in Turbo C++ (ver
- >2.00, I think) to this library?
-
- >Thanks for any help,
-
- >Tim Sullivan (sullivan@kenyon.edu)
-
-
- at one time, I contacted Borland Tech Support about this very same question.
- I think they gave me a legitimate answer, which stated that because of
- differences between Microsoft and Borland involving segments (CODE and DATA),
- unless you had the source code from Microsoft for the .OBJ's in the
- lib, there really wasn't a way to link Microsoft libs with Borland.
-
- Obvious answer. I never really delved into it again. I think that the
- other issue involves the startup code that each compiler uses to generate
- an executable. There might be stubs in the Microsoft lib's that refer to
- the startup code that in Borland's version do not exist or are stubbed
- differently.
-
- I don't know if this answers your question, but just some info to pass along.
-
- Jim
-
- --
- ------------------------------------------------------------------------------
- Jim Leary | My opinions are mine and do not reflect the opinions
- Progress Software | of my employer.
- ------------------------------------------------------------------------------
-