home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.tools
- Path: sparky!uunet!microsoft!hexnut!johnkal
- From: johnkal@microsoft.com (John Kallen)
- Subject: Re: MFC under BCC?
- Message-ID: <1992Aug11.020925.18514@microsoft.com>
- Date: 11 Aug 92 02:09:25 GMT
- Organization: Microsoft Applications Division (WGA)
- References: <59800002@otter.hpl.hp.com> <1992Aug05.012145.19837@microsoft.com>
- Lines: 31
-
- In article <59800002@otter.hpl.hp.com> slo@otter.hpl.hp.com (Steve Loughran) writes:
- :
- :However compilation ain't enough : I can't link to the library due to bad
- :object file records in SAFXCW.LIB.
- :A comparison of object files produced by MSC and BCC seems to indicate that
- :they are using different name mangling conventions.
- :
- :I wouldn't be suprised if I'm going to have to recompile the entire
- :foundation class library to have a hope of getting a simple MFC app to
- :work. I also get the sneaking suspicion that from now on sharing .obj files
- :from MSC to BCC isnt going to be as easy as it was when I was just importing
- :C functions.
- :
- : -Steve
-
- Borland and Microsoft have chosen two different name-mangling schemes for
- symbols. As you mention, this is unfortunate as it makes linking to .LIB
- libraries (as opposed to libraries where the source is provided) impossible
- if the library was built with the "wrong" version.
-
- With luck, a standard DOS/Win/OS-2 name-mangling will evolve. Until
- then, one will have to have sources to libraries, or compiler-vendor-dependent
- .LIB files (bleargh...)
- _______________________________________________________________________________
- | | | | |\ || /|\ | "Stonehenge is very nutritious" - Migato Gami
- | |\ \|/ \| * |/ ||/| | |
- | |\ /|\ |\ * |\ | | | | Microsoft couldn't care less about what I say.
- _|_|___|___|____|_\|__|_|__|____johnkal@microsoft.com__________________________
-
-
-
-